This guide provides instructions on how to use the new feature of our platform that allows the onboarding of multiple volumes from a single Virtual Machine (VM) to the AutoScaler.
Pre-requisites
Ensure that the Lucidity cloud agent has been installed on the VM.
Onboarding Process
Access the volumes to be onboarded from either the Onboard tab or the Unmanaged VMs page.
Choose the volume you wish to onboard, then click Onboard.
Enter the desired time window for onboarding and save your settings.
Once the volume has been successfully onboarded, you can proceed with onboarding the next volume.
However, please note that you need to wait until the previous volume (belonging to the same instance) has been successfully onboarded before you proceed onboarding the next volume.
Once the volumes have been successfully onboarded, they will start showing up under the Managed VM tab.
Limitations
Please be aware of the following limitations with the current implementation of this feature:
VM Restart
Each time a volume is onboarded, the associated VM will need to restart.
Multi-Mount Operations
Please note that instances onboarded prior to the feature release date (26-June-2023) have different support levels for multi-mount operations based on the operating system.
For Windows VMs: Multi-mount onboarding is supported for instances onboarded before the launch date. You can take advantage of the multi-mount feature for Windows VMs.
For Linux VMs: Multi-mount onboarding is not supported for instances onboarded before the launch date. If you have a Linux VM onboarded prior to the launch date and wish to utilize the multi-mount feature, we recommend creating a new instance.
Example: A single volume from an Ubuntu 20.04 OS instance was onboarded prior to 26th June 2023. In this case, it will NOT be possible to onboard other volumes belonging to the same instance.
Root Volume support
Please note that when using multi-mount features on Linux, it is important to onboard the root volume before the data partitions.
Example: A data volume from an Ubuntu instance is onboarded to the AutoScaler. In this case, it will NOT be possible to onboard any root volume belonging to the same Ubuntu instance. However, if the root volume is onboarded first, then data volumes from the same instance can still be onboarded.
AMI Instance Limitations
Instances spun out of an Amazon Machine Image (AMI) from a previously onboarded instance (pre - 26-June-2023) will not support the multi-mount onboarding feature.
Example: Instance was boarded on 24th June 2023. AMI was created from this instance. Instances spun out of this AMI and onboarded even after 26-June-2023 will NOT support multi mount point onboarding.
Configurations Replication
Configurations like 'disk encryption', 'deleteOnTermination', etc., will be sourced from the first onboarded volume. These settings will then be replicated on all subsequent volumes boarded from the same VM.
Example: ‘DeleteonTermination’ flag is set to TRUE for volume C and not for volumes D and E. In this case, if volume C is onboarded first then the flag will be set to true for volumes D and E as well post onboarding.