[
https://issues.apache.org/jira/browse/CLOUDSTACK-659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13555064#comment-13555064
]
Devdeep Singh edited comment on CLOUDSTACK-659 at 2/28/13 2:22 PM:
-------------------------------------------------------------------
The code is being developed and pushed to the following branch
https://github.com/devdeep/cloudstack.git
Update on the implementation completed:
Scenario 1 : Volume is live migrated to another storage pool while the virtual
machine continues to run on the same host
a. listStoragePoolsForMigration Api
This api will return a list of storage pools to which a given volume can be
migrated. The pools which have the right tags and sufficient capacity will be
marked as suitable. Implementation for this api is complete
b. migratVolume Api
It'll migrate a given volume to the specified storage pool. Implementation of
this api is complete.
Scenario 2 : Migrate a virtual machine to another host. The volumes of the
virtual machine also get migrated to another storage pool
a. listHostsForMigration
This api will list the hosts to which a given virtual machine can be migrated.
If the virtual machine is running on a host that supports storage motion, hosts
in other cluster and which support storage motion will also be listed. The
hosts that have sufficient capacity and the right tags are also marked as
suitable. Implementation of the api is complete.
b. migrateVirtualMachineWithVolumes
This api will migrate a virtual machine to a given host. It will optionally
take a parameter to migrate volumes of a virtual machine to given storage
pools. Migration of a virtual machine may happen within or across cluster.
Implementation for migrating a virtual machine along with its volumes with a
cluster is complete. For migrating across cluster implementaion is nearing
completion. Some additional changes on top of what is done for with cluster
needs to be made and tested.
What is pending.
1. The feature has been developed in a branch which was forked of master few
weeks ago. It needs to be merged into master on top of storage refactoring
changes. This is being done right now.
2. Unit tests have to be written too.
was (Author: devdeep):
The code is being developed and pushed to the following branch
https://github.com/devdeep/cloudstack.git
Update on the implementation completed:
Scenario 1 : Volume is live migrated to another storage pool while the virtual
machine continues to run on the same host
a. listStoragePoolsForMigration Api
This api will return a list of storage pools to which a given volume can be
migrated. The pools which have the right tags and sufficient capacity will be
marked as suitable. Implementation for this api is complete
b. migratVolume Api
It'll migrate a given volume to the specified storage pool. Implementation of
this api is complete.
Scenario 2 : Migrate a virtual machine to another host. The volumes of the
virtual machine also get migrated to another storage pool
a. listHostsForMigration
This api will list the hosts to which a given virtual machine can be migrated.
If the virtual machine is running on a host that supports storage motion, hosts
in other cluster and which support storage motion will also be listed. The
hosts that have sufficient capacity and the right tags are also marked as
suitable. Implementation of the api is complete.
b. migrateVirtualMachineWithVolumes
This api will migrate a virtual machine to a given host. It will optionally
take a parameter to migrate volumes of a virtual machine to given storage
pools. Migration of a virtual machine may happen within or across cluster.
Implementation for migrating a virtual machine along with its volumes with a
cluster is complete. For migrating across cluster implementaion is nearing
completion. Some additional changes on top of what is done for with cluster
needs to be made and tested.
What is pending.
1. The feature has been developed in a branch which was forked of master few
weeks ago. It needs to be merged into master on top of storage refactoring
changes.
2. Unit tests have to be written too.
> Enable storage xenmotion support in XenServer 6.1
> -------------------------------------------------
>
> Key: CLOUDSTACK-659
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-659
> Project: CloudStack
> Issue Type: New Feature
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Reporter: Devdeep Singh
> Assignee: Devdeep Singh
> Fix For: 4.2.0
>
>
> XenServer introduced support for Storage XenMotion in the latest version
> (6.1). Storage XenMotion allows VMs to be moved from one host to another,
> where the VMs are not located on storage shared between the two hosts. It
> provides the option to live migrate a VM’s disks along with the VM itself. It
> is now possible to migrate a VM from one resource pool to another, or to
> migrate a VM whose disks are on local storage, or even to migrate a VM’s
> disks from one storage repository to another, all while the VM is running.
> This issue is to track this feature request.
> Release Planning:
> Dev list discussions:
> http://markmail.org/message/numdk6pdab2hekdp
> http://markmail.org/message/cskrdafitghy7o6q
> Functional Spec:
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Enabling+Storage+XenMotion+for+XenServer
> Feature branch: via reviewboard
--
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
