[
https://issues.apache.org/jira/browse/CLOUDSTACK-2108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Srikanteswararao Talluri updated CLOUDSTACK-2108:
-------------------------------------------------
Assignee: Pranav Saxena
Summary: UI changes to support Storage XenMotion (was: UI changes for
support Storage XenMotion )
> UI changes to 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
> Assignee: Pranav Saxena
> 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
