provisioning_with_control_on_resources.md

Provisioning Oracle Database Sharding Topology with Additional Control on Resources Allocated to Pods

In this use case, there are additional tags used to control resources such as CPU and Memory used by the different Pods when the Oracle Sharding topology is deployed using Oracle Sharding controller.

This example uses shard_prov_memory_cpu.yaml to provision an Oracle Database sharding topology using Oracle Sharding controller with:

• Primary GSM Pods gsm1 and standby GSM Pod gsm2
• Two sharding Pods: shard1 and shard2
• One Catalog Pod: catalog
• Namespace: shns
• Tags memory and cpu to control the Memory and CPU of the PODs
• Additional tags INIT_SGA_SIZE and INIT_PGA_SIZE to control the SGA and PGA allocation at the database level

In this example, we are using pre-built Oracle Database and Global Data Services container images available on Oracle Container Registry

• To pull the above images from Oracle Container Registry, create a Kubernetes secret named ocr-reg-cred using your credentials with type set to kubernetes.io/dockerconfigjson in the namespace shns.
• If you plan to use images built by you, you need to change dbImage and gsmImage tag with the images you have built in your enviornment in file shard_prov_memory_cpu.yaml.
• To understand the Pre-requisite of Database and Global Data Services docker images, refer Oracle Database and Global Data Services Docker Images

Use the YAML file shard_prov_memory_cpu.yaml.

1. Deploy the shard_prov_memory_cpu.yaml file:

   kubectl apply -f shard_prov_memory_cpu.yaml

2. Check the details of a POD. For example: To check the details of Pod shard1-0:

   kubectl describe pod/shard1-0 -n shns

3. Check the status of the deployment:

   # Check the status of the Kubernetes Pods:
   kubectl get all -n shns
   
   # Check the logs of a particular pod. For example, to check status of pod "shard1-0":
   kubectl logs -f pod/shard1-0 -n shns