Page History

Bug Reference

tbd

Branch

tbd

Introduction

Users I want to be able to upgrade their data store datastore in vsphere vSphere and migrate existing VMs and data to the new storedatastore. For this they need to migrate stopped VMs and detached disks which is not possible at the moment. Vmware VMware does provide this functionality. The intention of this FS is to leverage vmwareVMware's functionality in via existing APIs.

References

• N/A

Glossary

Feature Specifications

• A stopped VM will be able to be migrated to an other datastore in vmwareVMware.

• A stand alone standalone volume stored on a primary storage (in vmwareVMware) will be able to be migrated to another storage in the same cluster.

cross Cross-cluster migrations are not supported. migrations Migrations will be checked for supported tags on the target datastore.

compatibility requirementsCompatibility Requirements:

this This is only applicable to VmwareVMware.

performance Performance for this feature is depending on dependent upon the underlying resources such as vsphere vSphere and esxi ESXi hosts, network bandwidth and datastore speed.

Use

...

Cases

migrating a Migrating an offline VM or volume is now a copy from primary to secondary and back to the new primary. This can be time consuming and will require requires large job timeouts. This can be cut in abpout about half by letting the hypervisor perform the migration directly.

Architecture and Design

...

Description

• for For offline VM migration, the existing API will be used. a A method finalizeMigration is created that returns a set of commands to execute on the resource to perform the migration. for VMWare For VMware this returns the needed commands. As default, as default a null will be returned indicating the hypervisor type can not cannot perform this function. (storage Storage migration is to be used in those cases.)
• for For detached volume migration, the vmware VMware storage migration stratgy strategy can return the priority of HYPERVISOR. For vmware VMware this would mean that the copyAsync call as implemented by storage migration strategies would actually do a full migration instad instead of a copy. The subsequetial subsequent delete is mute and will succeed as not needed.

Web Services APIs

No API will be changed to implement this functionality. The semantics of migrateVirtualMachine and migrateVolume will be changed in that these will now yield results on vmwareVMware, as opposed to yielding errors. 

UI flow

No UI change will be implemented

...

No usage impact is foreseen.

Appendix

Appendix A:

Appendix B: