Editing or scaling out an IBM Storage Scale cloud cluster

Scale out an IBM Storage Scale cloud cluster by using the cloudkit edit cluster command.

The cloudkit edit cluster command helps to increase the filesystem capacity of an existing IBM Storage Scale cloud cluster by performing:

Expansion of storage cluster instances
Expansion of compute cluster instances

Table 1. Instance maximum limit
Deployment profiles	Compute node limit	Storage node limit
Throughput-Performance-Persistent-Storage	64	64
Throughput-Performance-Scratch-Storage	64	64
Throughput-Advance-Persistent-Storage	64	10
Balanced	64	64

To expand a cluster, enter the following command:

#./cloudkit edit cluster

Example:

# ./cloudkit edit cluster

I: Logging at /root/scale-cloudkit/logs/cloudkit-26-7-2024_9-12-34.log
? Are you operating cloudkit in air-gapped or no-internet environment:  No
? Select a cluster:  ibm-storage-scale | None | us-central1 | GCP
? Select the role: Storage-only
I: Opted cluster 'ibm-storage-scale' is a 'Storage-only' cluster.
I: Opted cluster 'ibm-storage-scale' currently has '4' nodes.
? Storage node count:  6
I: Requested to expand the cluster by '2' node(s).
? Do you wish to view cost before provisioning the resources (this requires infracost api_key):  No
I: To edit this cluster again in the future, you can run:
        cloudkit edit cluster --airgap=false --region us-central1 --cloud-platform GCP --resource-name ibm-storage-scale --resource-group-ref None --view-cost=false --jumphost-login-user gcpuser --jumphost-asg-ref https://www.googleapis.com/compute/v1/projects/spectrum-scale-349401/zones/us-central1-c/instanceGroupManagers/ibm-storage-scale-bastion-asg --jumphost-private-key-path /root/scale-cloudkit/data/gcp/ibm-storage-scale/bastion_ssh_keys/id_rsa --jumphost-sec-ref ibm-storage-scale-bastion-tag --project-id xxxxxx-xxxx-xxxxx --credential-jsonpath /root/.config/gcloud/legacy_credentials/xxxxx@xxxxx-xxxx-xxxxx.iam.gserviceaccount.com/adc.json --strg-node-count 6 --role Storage-only

I: Past state of resources exists. Reusing it.
I: Initiating resource provisioning actions proposed in the scale instances IaC plan.
 100% |████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████| (10/10, 20 it/min)        
I: Cluster resource provisioning actions proposed in the plan completed.
 
I: Waiting for instances to obtain running state.
I: Initiating cluster configuration based on the provisioned resource inventory.
 100% |███████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████| (10/10, 2 it/min)          
I: IBM Storage Scale cluster configuration completed.
I: IBM Storage Scale cluster 'ibm-storage-scale' has been edited successfully.

Note: NSD disks are not balanced after an edit operation. If you want to rebalance the existing file system data across disks, run the mmrestripefs command.