Uploaded image for project: 'Migration Toolkit for Virtualization'
  1. Migration Toolkit for Virtualization
  2. MTV-1536

CDI for cold migration

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Major Major
    • 2.8.0
    • None
    • Controller, User Interface
    • None
    • CDI for cold migration
    • False
    • None
    • False
    • Hide
      - cold migration leverages CDI for import
      - @rjones is aware of this
      - docs state that vddk is mandatory
      - ui make vddk mandatory
      Show
      - cold migration leverages CDI for import - @rjones is aware of this - docs state that vddk is mandatory - ui make vddk mandatory
    • To Do
    • VIRTSTRAT-6 - Engineering Excellence
    • VIRTSTRAT-6Engineering Excellence
    • 100% To Do, 0% In Progress, 0% Done

      Right now we have 2 flows of the VMware migraitons.

      1. cold local migration
        1. Allocating the blank DataVolume
        2. CDI allocates the PVCs
        3. Conversion pod populates the PVCs and converts the pod both using the virt-v2v
      2. warm/remote migration
        1. Create the CDI DataVolume with the disk image
        2. CDI allocates the PVC
        3. CDI transferes the disk
        4. 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.

              mnecas@redhat.com Martin Necas
              mnecas@redhat.com Martin Necas
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: