Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cloudstack-dev@incubator.apache.org
Date: Thu, 28 Feb 2013 14:19:12 +0000 (UTC)
From: "Devdeep Singh (JIRA)" <jira@apache.org>
To: cloudstack-dev@incubator.apache.org
Message-ID: <JIRA.12624429.1355819682970.357897.1362061152713@arcas>
In-Reply-To: <JIRA.12624429.1355819682970@arcas>
References: <JIRA.12624429.1355819682970@arcas>
Subject: [jira] [Comment Edited] (CLOUDSTACK-659) Enable storage xenmotion
 support in XenServer 6.1
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/CLOUDSTACK-659?page=3Dcom.atlas=
sian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D=
13555064#comment-13555064 ]=20

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 https://gith=
ub.com/devdeep/cloudstack.git

Update on the implementation completed:

Scenario 1 : Volume is live migrated to another storage pool while the virt=
ual 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 migrat=
ed. If the virtual machine is running on a host that supports storage motio=
n, hosts in other cluster and which support storage motion will also be lis=
ted. The hosts that have sufficient capacity and the right tags are also ma=
rked 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 nearin=
g completion. Some additional changes on top of what is done for with clust=
er needs to be made and tested.

What is pending.
1. The feature has been developed in a branch which was forked of master fe=
w weeks ago. It needs to be merged into master on top of storage refactorin=
g changes.
2. Unit tests have to be written too.
               =20
      was (Author: devdeep):
    Started working on the implementation.

1. Made updates to migrateVirtualMachine api to allow migration of vm if th=
e hypervisor supports it.
2. Made db changes.
3. migrateVirtualMachine api will trigger migrate with storage if it is nee=
ded.
4. Implemented a ReceiveStorageMigration command in Xenserver 6.1 resource =
base. It does the work of sending a migrate receive to destination, then op=
ens a connection to the source and sends a assertCanMigrate and migrate sen=
d command to the source host.
5. Updated the delta sync code to put the right state of the vm after stora=
ge xenmotion.
6. Working on updating the allocator to list the host that can be used for =
migration with storage.
                 =20
> 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 defa=
ult.)=20
>            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, w=
here the VMs are not located on storage shared between the two hosts. It pr=
ovides the option to live migrate a VM=E2=80=99s disks along with the VM it=
self. 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=E2=80=99s 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/E=
nabling+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 administrato=
rs
For more information on JIRA, see: http://www.atlassian.com/software/jira