Increasing SDS disk size for a node

Last Updated : Aug 13, 2024 |
Prolog information
This procedure increases the Software-Defined Storage (SDS) disk size for all disk nodes in the cluster. You cannot decrease SDS disk size.
Note:
vCenter does not enable you to resize SDS disks on virtual machines that have snapshots. To resize an SDS disk, remove any virtual machine snapshots before proceeding with this procedure.
  1. Resize the SDS disk in vCenter.
    ADDITIONAL INFORMATION:
    This step can be done without powering off the cluster nodes.
  2. Log in to Cluster Control Manager with an account that has root privileges.
  3. On Cluster Control Manager, run the following command:
    ADDITIONAL INFORMATION:
    kubectl exec --namespace=piraeus deployment/piraeus-op-piraeus-operator-cs-controller -linstor sp l
  4. Note the nodes that have a storage pool of pool_sds.
  5. Open the VMware Infrastructure client and log in to vCenter or the ESX host machine.
  6. Right-click the cluster node VM from the output above.
  7. Click Edit settings.
  8. Select Virtual Disk.
    ADDITIONAL INFORMATION:
    This is Hard Disk 2, with a size similar to the SDS Disk Size in current solution spreadsheet.
  9. Enter the new size for the virtual hard disk based on the footprint summary table in the updated deployment spreadsheet.
  10. Run the ccm upgrade spec <solution spreadsheet name>.xlsx --infra command.
  11. Wait approximately 30 minutes, then run ccm smoke-test on Cluster Control Manager and confirm that all tests pass. If ccm smoke-test fails, run it again in 10 minutes. If the test continuously fails for over an hour, contact your technical support representative.
  12. To verify the new disk size, run the checkInfra -Sd command and review the SDS capacity.
    . . .
    Storage pools:
    +----------------------------------------------------------------------------------------------------------------------------------------------------+
    | StoragePool          | Node                   | Driver   | PoolName            | FreeCapacity | TotalCapacity | CanSnapshots | State | SharedName |
    |====================================================================================================================================================|
    | DfltDisklessStorPool | flex190-78.example.com | DISKLESS |                     |              |               | False        | Ok    |            |
    | DfltDisklessStorPool | flex190-79.example.com | DISKLESS |                     |              |               | False        | Ok    |            |
    | DfltDisklessStorPool | flex190-80.example.com | DISKLESS |                     |              |               | False        | Ok    |            |
    | DfltDisklessStorPool | flex190-94.example.com | DISKLESS |                     |              |               | False        | Ok    |            |
    | pool_sds             | flex190-78.example.com | LVM_THIN | vg_sds/sds_thinpool |   521.02 GiB |    599.70 GiB | True         | Ok    |            |
    | pool_sds             | flex190-79.example.com | LVM_THIN | vg_sds/sds_thinpool |   526.18 GiB |    599.70 GiB | True         | Ok    |            |
    +----------------------------------------------------------------------------------------------------------------------------------------------------+
    . . .
Result
After the upgrade completes, the cluster nodes have access to the increased SDS disk capacity.