Resizing the Virtual Hard Disk After Deployment
You can use the cloud provider's tools to resize a virtual CipherTrust Manager instance's hard disk size after deployment.
Disk Resize Available with Disk Encryption
After you launch an unencrypted Virtual CipherTrust Manager and disable the cloud-init service, you cannot resize the disk. If you require a Virtual CipherTrust Manager with a larger or smaller disk size:
Encrypt the disk for the Virtual CipherTrust Manager instance and then attempt re-size.
Take a backup on the existing Virtual CipherTrust Manager, deploy a new Virtual CipherTrust Manager instance with the desired disk size, and restore the backup file on the new instance.
If you have applied disk encryption, you need a ksctl connection to unlock the instance after resizing.
Resizing an instance
Shut down the Guest OS or power off the virtual CipherTrust Manager instance.
Use the cloud provider's tooling to resize the hard disk.
For Amazon Web Services, under Actions, select Modify Volume, edit the Size field, and select Modify. Check Amazon EC2 documentation for more details.
For Google cloud, follow Google Cloud documentation.
For Microsoft Azure, consult Microsoft Azure documentation.
For Microsoft Hyper-V, consult Microsoft Hyper-V documentation.
For Nutanix AHV, consult Nutanix documentation.
For Oracle Cloud, consult Oracle Documentation.
In VMware vSphere, right click the virtual CipherTrust Manager instance, select Edit Settings, and adjust the Hard disk size. Consult VMware vSphere documentation for more details.
Note
The resulting disk size will be slightly smaller (within 2 GB) of the setting you apply here.
Power the device back on.
If the disk was encrypted, booting pauses until you secure boot with the following command:
The instance resumes booting.
To confirm the disk resize:
Use the Web Console for SSH access to the instance.
Login the
ksadmin
user.Run the following command to display the disk size used
df -h /
.