cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Devdeep Singh (JIRA)" <>
Subject [jira] [Comment Edited] (CLOUDSTACK-659) Enable storage xenmotion support in XenServer 6.1
Date Thu, 28 Feb 2013 14:19:12 GMT


Devdeep Singh edited comment on CLOUDSTACK-659 at 2/28/13 2:17 PM:

The code is being developed and pushed to the following branch

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

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.
      was (Author: devdeep):
    Started working on the implementation.

1. Made updates to migrateVirtualMachine api to allow migration of vm if the hypervisor supports
2. Made db changes.
3. migrateVirtualMachine api will trigger migrate with storage if it is needed.
4. Implemented a ReceiveStorageMigration command in Xenserver 6.1 resource base. It does the
work of sending a migrate receive to destination, then opens a connection to the source and
sends a assertCanMigrate and migrate send command to the source host.
5. Updated the delta sync code to put the right state of the vm after storage xenmotion.
6. Working on updating the allocator to list the host that can be used for migration with
> Enable storage xenmotion support in XenServer 6.1
> -------------------------------------------------
>                 Key: CLOUDSTACK-659
>                 URL:
>             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:
> Functional Spec:
> 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:

View raw message