Got it. Cool, thanks.
David La Motta Technical Marketing Engineer Citrix Solutions NetApp 919.476.5042 dlamo...@netapp.com<mailto:dlamo...@netapp.com> On Jun 7, 2013, at 11:28 AM, kel...@backbonetechnology.com<mailto:kel...@backbonetechnology.com> <kel...@backbonetechnology.com<mailto:kel...@backbonetechnology.com>> wrote: Migration is only achievable in a cluster. It is hypervisor dependant. Migration is used only for CAP management and HA. In order to cross the hypervisor barrier you need to automate the 'create template > export template > convirt template > import template > provision' process. Sent from my HTC ----- Reply message ----- From: "La Motta, David" <david.lamo...@netapp.com<mailto:david.lamo...@netapp.com>> To: "<dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>>" <dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>> Subject: migrateVirtualMachine Date: Fri, Jun 7, 2013 8:20 AM Anybody know a bit more in depth what that API call really does? From the API docs it "Attempts Migration of a VM to a different host or Root volume of the vm to a different storage pool". Does this mean if the VM is on XenServer and I want to move it to vShpere, it does VHD to OVA (VMDK?) conversion under the covers? Just trying to understand this a bit better. Thanks. David La Motta Technical Marketing Engineer Citrix Solutions NetApp 919.476.5042 dlamo...@netapp.com<mailto:dlamo...@netapp.com>
