Background
Some customers have VMs that need to be migrated with virtual disks of substantial size. Performing migrations on these guests can take a very long time or fail due to network errors.
An idea we had was to:
- create a NFS share via Manila and present that to VMWare as a datastore path.
- while the VM is still running in VMware perform a storage live migration to from the vSAN to the Manila presented NFS share store.
- perform the vm migration with os-migrate
The advantage here is that the storage can be migrated from the VMware vSAN (or other non openstack storage array) to an OpenStack storage backend and openstack local network before the VM is disrupted by the migration (reducing overall effort/duration). Eg. moving data in-array would generally be preferable than a dis-aggregated streaming from the DC at large, or from VMware hosts whos management network may not support performant network transfers.
What we need
We need OS-Migrate to consider (either by manual/administrative invocation or by autodetecting the disk path from a known list) that the VM data disks dont need to be exported from the ESX host.
Background
Some customers have VMs that need to be migrated with virtual disks of substantial size. Performing migrations on these guests can take a very long time or fail due to network errors.
An idea we had was to:
The advantage here is that the storage can be migrated from the VMware vSAN (or other non openstack storage array) to an OpenStack storage backend and openstack local network before the VM is disrupted by the migration (reducing overall effort/duration). Eg. moving data in-array would generally be preferable than a dis-aggregated streaming from the DC at large, or from VMware hosts whos management network may not support performant network transfers.
What we need
We need OS-Migrate to consider (either by manual/administrative invocation or by autodetecting the disk path from a known list) that the VM data disks dont need to be exported from the ESX host.