You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Srikanteswararao Talluri (JIRA)" <ji...@apache.org> on 2013/04/19 09:21:15 UTC
[jira] [Created] (CLOUDSTACK-2108) UI changes for support Storage
XenMotion
Srikanteswararao Talluri created CLOUDSTACK-2108:
----------------------------------------------------
Summary: UI changes for support Storage XenMotion
Key: CLOUDSTACK-2108
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2108
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: UI
Affects Versions: 4.2.0
Reporter: Srikanteswararao Talluri
Fix For: 4.2.0
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Enabling+Storage+XenMotion+for+XenServer#EnablingStorageXenMotionforXenServer-FeatureSpecification
- Changes required in UI for live migrating a volume from one storage pool to another.
1. UI needs to be updated to allow migration of a volume even if it is attached to a running vm.
2. UI will be updated to make a listStoragePoolsForMigration call for volumes; root or datadisk; to get the list of storage pools available.
3. For live migrating a volume, migrateVolume call will be made with volumeid, storageid passed as a parameter. The livemigrate parameter should also be set to true.
- Changes required in UI for live migrating an instance along with its volume.
1. Currently UI makes a listHosts api call with virtualmachineid as a parameter to get the list of hosts to which a vm can be migrated.
2. UI will be instead updated to make a listHostsForMigration call.
3. If migration of an instance to a host requires storage motion; as indicated in the response object by the requiresStorageMotion field; UI will make a migrateVirtualMachineWithVolume api call. The virtual machine id and host id are passed as the parameters.
Challenges I see here are :
1. This is a hypervisor specific feature: XenServer6.1, Hence, we need to be carefule while dealing with VMs on other hypervisors
feature tracking bug for Storage XenMotion: https://issues.apache.org/jira/browse/CLOUDSTACK-659
It is yet to be checked in.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira