Chapter 1. Infrastructure Migration Solution Overview

Red Hat’s Infrastructure Migration Solution (IMS) enables you to migrate your virtual machines from VMware to Red Hat Virtualization.

Red Hat Virtualization (RHV) is an enterprise-grade virtualization platform built on Red Hat Enterprise Linux. With Red Hat Virtualization, you can manage your entire virtual infrastructure, including hosts, virtual machines, networks, storage, and users, from a centralized graphical user interface or with a REST API. The IMS user interface, Red Hat CloudForms, provides the control and automation required to manage challenging enterprise environments.

Currently, IMS supports only cold migration. The virtual machines are powered off gracefully as part of the migration process.

IMS Phases

The Infrastructure Migration Solution has 4 key phases:

  1. Planning the migration:

    1. Consult the planning questions to ensure that you have sufficient resources for the migration.
    2. Follow best practices to minimize the impact on your users. You may choose to schedule the migration in phases or to create groups of virtual machines that should migrate together.
  2. Preparing the migration environment:

    1. Create and configure the source and target environments.
    2. Create and configure the RHV conversion host(s).
  3. Migrating the infrastructure:

    1. Map your source environment to the target environment, selecting the virtual machines to migrate.
    2. Create and run a migration plan, with optional automated pre- and post-migration tasks.
  4. Verifying the migration:

    1. Check the completed migration plan for successfully migrated virtual machines.
    2. If errors appear, see Chapter 5, Troubleshooting.

Workflow: VMware to Red Hat Virtualization

This workflow occurs when you run a migration plan to migrate your infrastructure from VMware to Red Hat Virtualization.

vmware to rhv migration workflow

  1. After creating an infrastructure mapping and a migration plan in CloudForms, you run the migration plan.
  2. CloudForms locates the virtual machines to be migrated based on the infrastructure mapping.
  3. The ESXi host fingerprint is captured for authentication during the conversion process if the VDDK transport method is used. If SSH is used, a shared SSH key is used to connect to the ESX host where the virtual machine resides.
  4. Using the RHV attributes for the target environment, CloudForms initiates communication with the RHV conversion host.
  5. The RHV conversion host connects to the source datastore through the ESX host, using virt-v2v-wrapper.py, and streams the disk to be converted to the target data domain chosen in the infrastructure mapping using virt-v2v.
  6. After the disk is converted, the target virtual machine is created in RHV. During creation, the target virtual machine uses the source virtual machine’s metadata to maintain the virtual machine’s attributes (tags, power state, MAC address, CPU count, memory, disks, and virtual machine name) after migration.
  7. After the virtual machine is created, the disk is attached to the target virtual machine.

The virtual machine migration is complete and its status is displayed in CloudForms.

Note

Depending on the source virtual machine’s power state before migration, the virtual machine is either left powered off after migration or is powered on.