-
Epic
-
Resolution: Done
-
Normal
-
None
-
None
-
None
-
CDI for cold migration
-
Quality / Stability / Reliability
-
False
-
-
False
-
- cold migration leverages CDI for import
- @rjones is aware of this
- docs state that vddk is mandatory
- ui make vddk mandatory
-
In Progress
-
VIRTSTRAT-6 - Engineering Excellence
-
-
0% To Do, 0% In Progress, 100% Done
Right now we have 2 flows of the VMware migraitons.
- cold local migration
- Allocating the blank DataVolume
- CDI allocates the PVCs
- Conversion pod populates the PVCs and converts the pod both using the virt-v2v
- warm/remote migration
- Create the CDI DataVolume with the disk image
- CDI allocates the PVC
- CDI transferes the disk
- The conversion pod only runs the virt-v2v-in-place and only converts the guest
We are using 2 different flows which can cause problems with different behavior. For example the CDI transfers each disk in parallel whereas the virt-v2v transfers the disks in sequence. So the migration of single VM with multiple disks could be faster using the warm/remote migration flow.
We should investigate if it would be worth if to migrate into single flow using the CNV CDI.