In this use case, an existing OCI DBCS system deployed earlier is scaled up for its storage using Oracle DB Operator DBCS controller. Its a 2 Step operation.
In order to scale up storage of an existing DBCS system, the steps will be:
- Bind the existing DBCS System to DBCS Controller.
- Apply the change to scale up its storage.
NOTE We are assuming that before this step, you have followed the prerequisite steps to create the configmap and the secrets required during the deployment.
This example uses scale_up_storage.yaml
to scale up storage of an existing Single Instance DBCS VMDB using Oracle DB Operator DBCS Controller with:
- OCID of existing VMDB as
ocid1.dbsystem.oc1.phx.anyhqljrabf7htyanr3lnp6wtu5ld7qwszohiteodvwahonr2yymrftarkqa
- OCI Configmap as
oci-cred
- OCI Secret as
oci-privatekey
- Availability Domain for the DBCS VMDB as
OLou:PHX-AD-1
- Compartment OCID as
ocid1.compartment.oc1..aaaaaaaa4hecw2shffuuc4fcatpin4x3rdkesmmf4he67osupo7g6f7i6eya
- Database Admin Credential as
admin-password
- Database Hostname Prefix as
host0130
- Target Data Storage Size in GBs as
512
- Oracle VMDB Shape as
VM.Standard2.1
- SSH Public key for the DBCS system being deployed as
oci-publickey
- OCID of the Subnet as
ocid1.subnet.oc1.phx.aaaaaaaauso243tymnzeh6zbz5vkejgyu4ugujul5okpa5xbaq3275izbc7a
Use the file: scale_up_storage.yaml for this use case as below:
- Deploy the .yaml file:
[root@test-server DBCS]# kubectl apply -f scale_storage.yaml
dbcssystem.database.oracle.com/dbcssystem-existing configured
- Monitor the Oracle DB Operator Pod
pod/oracle-database-operator-controller-manager-665874bd57-g2cgw
for the progress of the DBCS VMDB Scale up.
NOTE: Check the DB Operator Pod name in your environment.
[root@docker-test-server DBCS]# kubectl logs -f pod/oracle-database-operator-controller-manager-665874bd57-g2cgw -n oracle-database-operator-system
Here is the sample output for scaling up the storage of an existing DBCS System deployed in OCI using Oracle DB Operator DBCS Controller with minimal parameters.