You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Sateesh Chodapuneedi (JIRA)" <ji...@apache.org> on 2013/05/27 16:55:21 UTC

[jira] [Created] (CLOUDSTACK-2701) Enable storage migration for VMware resources

Sateesh Chodapuneedi created CLOUDSTACK-2701:
------------------------------------------------

             Summary: Enable storage migration for VMware resources
                 Key: CLOUDSTACK-2701
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2701
             Project: CloudStack
          Issue Type: Improvement
      Security Level: Public (Anyone can view this level - this is the default.)
          Components: VMware
    Affects Versions: 4.2.0
            Reporter: Sateesh Chodapuneedi
            Assignee: Sateesh Chodapuneedi
             Fix For: 4.2.0


Storage vMotion allows VMs to be moved from one host to another, along with storage across datastores in datacenter. 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 datastore to another, or even to migrate a VM’s disks from one datastore to another with VM running on same host, all while the VM is running. 

This issue is to track the support of storage vMotion for VMware resources in cloudstack. Till now ticket CLOUDSTACK-659 was using in all code commits done to branch vmware-storage-motion. Just now created this ticket to deal with specific areas in implementation that is well contained and limited to VMware resource only. Commits related to VmwareStorageMotionStrategy class and it's implementation along with commands MigrateWithStorageCommand and MigrateVolumeCommand are done under CLOUDSTACK-659 ticket.

Release Planning: 
Functional Spec: https://cwiki.apache.org/confluence/display/CLOUDSTACK/Enabling+Storage+XenMotion+for+XenServer (section VMware resource)
Feature branch: vmware-storage-motion

--
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