Bug Reference
CLOUDSTACK-6143
...
- Only a root admin can migrate a volume from one storage pool to another.
- Only a root admin can migration a virtual machine with its volume.
Supported Hypervisor
This feature is implemented for Windows Server 2012 R2 and Hyper-V 2012 R2 (Core).
Use cases
Architecture and Design description
...
Since these are existing apis; they are not explained here. Please refer to Storage motion in cloudstack for api details.
UI flow
No new UI screens are introduced by this feature. Also, no changes need to be made in UI for adding support for storage motion in Hyper-V. The UI workflow looks as follows.
Migrating Volume
- From the Storage option in admin UI, select the volume that is attached to a running vm and has to be live migrated.
- Select the migrate option. 'findStoragePoolsForMigration' api is invoked by the UI. This will give a list of shared pools available to which the volume can be migrated.
- Selecting one of the storage pools and selecting ok will trigger the 'migrateVolume' api to migrate the volume.
Migrate virtual machine with volume
- From the Instances option in the admin UI, select the instance that needs to be migrated (with its volumes).
- Select the migrate option. 'findHostsForMigration' api is invoked by the UI. This will give a list of hosts to which the vm can be migrated.
- If migrating to a host requires storage motion too, 'requiresStorageMotion' flag is set to true in the response and the UI shows it as "Storage migration required".
- Selecting a host; to which storage mition is required; will trigger the 'migrateVirtualMachineWithVolume' api.either demonstrate it visually here or link to relevant mockups
IP Clearance
No IP dependencies are introduced by this feature.
...