ExaCC: Scale Your VM Cluster Memory Using OCI CLI

Share on:

This blog post will be a short one, but I think it is very useful when scaling your resources in an ExaCC Environment.

The first thing I do is find out how much memory the VM Cluster has, which in my case it is 1900 GB.

Rene@eclipsyss-mbp eclipsys % oci db vm-cluster get --vm-cluster-id ${VM_CLUSTER_OCID} | jq -r .data.\"display-name\",.data.\"memory-size-in-gbs\",.data.\"lifecycle-state\"
exaccrene1db
1900
AVAILABLE

I will now scale the VM Cluster to 2000 GB, which is what was required for this exercise.

Rene@eclipsyss-mbp eclipsys % export VM_CLUSTER_OCID=ocid1.vmcluster.oc1.ca-toronto-1.aaaaaaaabbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Rene@eclipsyss-mbp eclipsys % oci db vm-cluster update --vm-cluster-id ${VM_CLUSTER_OCID} --memory-size-in-gbs 2000 --wait-for-state AVAILABLE --wait-interval-seconds 10
Action completed. Waiting until the resource has entered state: ('AVAILABLE',)
Failed to wait until the resource entered the specified state. Outputting last known resource state
{
   "data": {
      "compartment-id": "ocid1.compartment.oc1..aaaaaaaabbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb",
      "cpus-enabled": 4,
   ...
   "memory-size-in-gbs": 1900,
      "opc-work-request-id": "ocid1.coreservicesworkrequest.oc1.ca-toronto-1.aaaaaaaabbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb"
}

As you saw in the message above, the command exited before the memory changed in the VM cluster. This doesn’t mean that we failed to scale the cluster, it just means that the command exited before having an AVAILABLE status. We just need to wait a bit for the scale to happen and we will now see the new values of memory in our ExaCC VM Cluster.

Rene@eclipsyss-mbp eclipsys % oci db vm-cluster get --vm-cluster-id ${VM_CLUSTER_OCID} | jq -r .data.\"display-name\",.data.\"memory-size-in-gbs\",.data.\"lifecycle-state\"
exaccrene1db
2000
UPDATING
Rene@eclipsyss-mbp eclipsys % oci db vm-cluster get --vm-cluster-id ${VM_CLUSTER_OCID} | jq -r .data.\"display-name\",.data.\"memory-size-in-gbs\",.data.\"lifecycle-state\"
exaccrene1db
2000
AVAILABLE

As I mentioned, this was going to be a short blog post, but hope it helps you whenever you need to scale your ExaCC VM Clusters.

Share on:

More from this Author

OCI, Terraform & IaC Creating Compartments for CIS Foundation Architecture by Gustavo

OCI, Terraform & IaC: Creating Compartments for CIS Foundation Architecture

In this third blog post series, we will be creating four main compartments Security Compartment Network Compartment App/Dev Compartment Database ... Read More

OCI, Terraform & IaC Creating a Compartment

OCI, Terraform & IaC: Creating a Compartment

In my previous post, I talked about the setup of Terraform and a primer on what it is. In this blog post, I will create a simple resource in OCI. One ... Read More

Back to Top