DocsKnowledge BaseAPI Explorer
Documentation›ZCF›ZStack Cloud›Explore more›V2V Migration TutorialZCF

Overview

ZStack Cloud provides the Migration Service, allowing you to migrate VM systems and data from other virtualization platforms to the current cloud. Currently, with the Migration Service, you can:
  • Migrate VM instances from the vCenter that you took over to the current cloud. The supported vCenter versions include 5.5, 6.0, 6.5, 6.7, and 7.0. Note that the version of the vCenter server must be consistent with that of the ESXi host.
  • Migrate VM instances from a KVM cloud platform to the current cloud.
    Note: If you took over vCenter 7.0, to ensure that the VM console can open properly, we recommend that you download the trusted root CA certificate when you log into vCenter.
Figure 1. V2V Migration




The Migration Service is a separate feature module. To use this feature, you need to purchase both the Base License and the Plus License of the Migration Service. The Plus License cannot be used independently.

Advantages of the Migration Service are as follows:
  • Allows you to perform one-click V2V migrations for VM instances in bulk.
  • Allows you to add a conversion host and create a V2V job and lets the Cloud do the rest.
  • Allows you to configure an independent migration network and a network QoS for a conversion host to control transmission bottlenecks and improve migration efficiencies.
  • Allows you to customize configurations for destination VM instances when you create a V2V job.
  • Monitors and manages the entire migration process in the visualized, well-designed UI.

Preparations

  • The admin installs the latest version of ZStack Cloud in advance, and deploys necessary resources used for creating VM instances.

    For more information, see the Installation and Deployment section in the User Guide.

  • The admin purchases a Plus License of the Migration Service module in advance, and then installs this module.
  • If the source cloud platform is VMware, take over the vCenter to ZStack CloudPrivate Cloud.

Quick Start

You can quickly get started with the migration service by following these steps:
  1. Add a V2V conversion host. For information about how to add a V2V conversion host, see V2V Conversion Host.
  2. Create a V2V job to migrate VM instances from other virtualization platforms to the current cloud. For information about how to create a V2V job, see V2V Migration.

V2V Migration

Currently, you can migrate VM instances from a VMware cloud platform or a KVM cloud platform to the current cloud. Before you use the Migration Service, note the following considerations.

VMware Source Platform Considerations

If the source cloud platform is VMware, note the following:
  • Before migrations, perform data synchronization to manually synchronize the latest status of resources in the vCenter that you took over.
  • You can perform bulk V2V migrations for VM instances, and customize configurations of the migrated VM instances.
  • The supported vCenter versions include 5.5, 6.0, 6.5, 6.7, and 7.0. Note that the version of the vCenter server must be consistent with that of the ESXi host.
  • The supported VM systems of the source vCenter include RHEL/CentOS 4.x, 5.x, 6.x, 7.x, SLES 11, 12, 15, Ubuntu 12, 14, 16, 18, Windows 7, and Windows Server 2003 R2, 2008 R2, 2012 R2, 2016, 2019.
  • The VM instances will be forced to shut down during the V2V migration. Therefore, pay attention to the business impact.
    Note: The system firstly attempts to shut down the VM instances gently. If the shutdown fails, the system will perform force shutdown.
  • The type of the source primary storage is not enforced. The type of the destination primary storage can be LocalStorage, NFS, Ceph, or SharedBlock.
  • For Windows VM instances, the Windows VirtIO driver is automatically installed during the migration. This improves the NIC and disk efficiencies.
  • You can perform V2V migration for VM instances booted by UEFI. After the migration, these VM instances are also booted by UEFI.

KVM Source Platform Considerations

If the source cloud platform is KVM, note the following:
  • You can perform bulk V2V migrations for VM instances, and customize configurations of the migrated VM instances.
  • You can migrate the VM instances that are running or paused. Do not power off the VM instances to be migrated.
  • You can perform V2V migrations for VM instances booted by UEFI. After the migration, these VM instances are also booted by UEFI.
  • The type of the source primary storage is not enforced. The type of the destination primary storage can be LocalStorage, NFS, Ceph, or SharedBlock.
  • For different types of source primary storages or destination primary storages, the libvirt version and QEMU version must meet the following requirements:
    • If either the source primary storage or destination primary storage is Ceph, use libvirt 1.2.16 and QEMU 1.1 or their later versions.
    • If neither the source primary storage nor destination primary storage is Ceph, use libvirt 1.2.9 and QEMU 1.1 or their later versions.

Source Cloud Platform: VMware

This topic describes VMware-based V2V jobs from the following perspectives:

Create a V2V Job

To create a V2V job based on the VMware platform, follow these five steps:
  1. Configure the source resources.
    Set the following parameters:
    • Name: Enter a name for the V2V job.

      The name must be 1 to 128 characters in length and can contain Chinese characters, letters, digits, spaces, hyphens (-), underscores (_), periods (.), parenthesis (), colons (:), and plus signs (+) and cannot begin or end with spaces.

    • Description: Optional. Enter a description for the V2V job.
    • Source Platform: Select the source platform type. Here, select VMware.
    • V2V Conversion Host: Select a V2V conversion host.
      Note:
      • Before you can create a V2V job, add a V2V conversion host to the Cloud.
      • The type of the V2V conversion host must be consistent with that of the source cloud platform.
      • The V2V conversion host is a host in the specified destination cluster. Make sure that the hardware resources are sufficient for V2V migration.
      • If you select multiple source VM instances, note that the V2V jobs created accordingly will share the same V2V conversion host.
    • Source Cluster: Select a cluster from the vCenter that you took over as the source cluster.
    • Source VM: Select one or more vCenter VM instances from the source cluster as the source VM instance or VM instances. You can select up to 50 VM instances at a time.
      Note:
      • If you select more than one VM instance, corresponding V2V jobs will be created in bulk. Note that one V2V job corresponds to one source VM instance.
      • For Windows Server 2012 R2 and Windows Server 2016 VM instances, you need to manually disable the hibernation feature and shut down these VM instances before you create V2V jobs.
        To disable or enable the Windows hibernation feature, run the following commands:
        • Disable Windows hibernation: cmd-->“powercfg -h off”
        • Enable Windows hibernation: cmd-->“powercfg -h on”
      • If one of the source VM instances has a data volume, make sure that the disk mode of the data volume is Dependent. Otherwise, the V2V job might fail.
    Figure 2. Configure Source Resources


  2. Configure the destination resources.
    Set the following parameters:
    • Destination Zone: By default, the current zone is displayed.
    • Destination Cluster: Select a destination cluster. Then, the estimated CPU usage and memory usage are displayed.
      • Estimated CPU usage: displays the number of the used CPUs of the source VM instance and the total number of available CPUs in the destination cluster.
      • Estimated memory usage: displays the used memory size of the source VM instance and the total available memory size in the destination cluster.
    • Destination Primary Storage: Select a destination primary storage. Then, the estimated primary storage usage is displayed.
      • Estimated storage usage: displays the used storage of the source VM instance and the total available storage of the destination primary storage.
    • Compression mode: Choose whether to enable the compression mode. By default, the compression mode is enabled.
      Note:
      • Enabling the compression mode compresses the caches of the migration data and improves the cache space utilization of the V2V conversion host.
      • If the destination primary storage is Ceph, we recommend that you do not use the compression mode.
    Figure 3. Configure Destination Resources


  3. Configure the network mapping.
    In this step, consider the following:
    • The source VM instance has a NIC attached.
    • The source VM instance does not have a NIC attached.
    1. If the source VM instance has a NIC attached,
      Set the following parameters:
      • Destination Network: Select a destination network as needed. The destination network is the network attached to the specified destination cluster.
    2. If the source VM instance does not have a NIC attached, go to the next step to manually configure the destination NIC.
    Figure 4. Configure Network Mapping


  4. Configure the destination VM instance.
    In this step, consider the following:
    • The VM instance has a NIC attached.
    • The VM instance does not have a NIC attached.
    1. If the VM instance has a NIC attached,
      configure the destination VM instance by setting the following parameters:
      • Start VM After Migration: Choose whether to automatically start the destination VM instance after the migration.
      • Use Source MAC and IP: Choose whether to use the source MAC and IP addresses. By default, these addresses are not used.
        Note:
        • If not used, you can customize the MAC and IP addresses for the destination NIC. If you do configure them, the destination MAC address will be the same as the source MAC address after migration, and the IP address of the destination NIC will be allocated by the system.
        • If used, the destination NIC will use the MAC and IP addresses of the source NIC in the next step. If the source NIC does not have an IP address, the IP address of the destination NIC will be allocated by the system.
      • VM Configuration: Select the VM instance to be configured. You can configure the VM instance by setting the following parameters:
        • Name: Set the name of the destination VM instance.
        • NIC: Configure the NIC information.
          • Network: Select the network for the destination VM instance.
          • IP Address: Optional. Configure the IP address of the destination NIC.
            Note: If not configured, the IP address of the destination NIC will be allocated by the system.
          • MAC Address: Optional. Configure the MAC address of the destination NIC.
            Note: If not configured, the MAC address of the destination NIC will be the same as that of the source NIC after migration.
      • Boot Partition: If the VM instance to be migrated has multiple boot partitions, specify one as the root volume for the VM instance.
      Note:
      • Go to the next step if no further modification is needed.
      • Before you migrate a VM instance to the current cloud, make sure that the VM instance has at least one NIC attached.
    2. If the VM instance does not have a NIC attached,
      configure the destination VM instance by setting the following parameters:
      • Start VM After Migration: Choose whether to automatically start the destination VM instance after the migration.
      • VM Configuration: Select the VM instance to be configured. You can configure the VM instance by setting the following parameters:
        • Name: Set the name of the destination VM instance.
        • NIC: Configure the NIC information.
          • Network: Select the network for the destination VM instance.
          • IP Address: Optional. Configure the IP address of the destination NIC.
          • Note: If not configured, the IP address of the destination NIC will be allocated by the system.
          • MAC Address: Optional. Configure the MAC address of the destination NIC.
            Note: If not configured, the MAC address of the destination NIC will be the same as that of the source NIC after migration.
        • Boot Partition: If the VM instance to be migrated has multiple boot partitions, specify one as the root volume for the VM instance.
      Note: Before you migrate a VM instance to the current cloud, make sure that the VM instance has at least one NIC attached.
    Figure 5. Configure Destination VM


  5. Confirm and submit.
    Figure 6. Confirm and Submit


Manage a V2V Job

On the main menu of ZStack Cloud, choose Platform O&M > Migration Service > V2V Migration. Then, the V2V Migration page is displayed.

The following table lists the actions that you can perform on a V2V job.
Action Description
Reboot V2V Job Reboot a V2V job if the job failed.
Note:
  • If migration data caches exist, rebooting the V2V job can improve the migration efficiency.
  • You can set the period for retaining the migration data caches in the global setting.
Edit V2V Job Modify the name and description of a V2V job.
Delete V2V Job Delete a V2V job after migration.

V2V Job Details

On the V2V Migration page, click on the name of a V2V job. Then, the details page of the V2V job is displayed. On the details page, you can view the V2V job status and the basic information about the source VM instance and destination VM instance.

Figure 7. V2V Job Details


Source Cloud Platform: KVM

This topic describes KVM-based V2V jobs from the following perspectives:

Create a V2V Job

To create a V2V job based on the KVM platform, follow these five steps:
  1. Configure the source resources.
    Set the following parameters;
    • Name: Enter a name for the V2V job.
    • Description: Optional. Enter a description for the V2V job.
    • Source Platform: Select KVM.
    • V2V Conversion Host: Specify a V2V conversion host.
      Note:
      • Before you can create a V2V job, add a V2V conversion host to the Cloud.
      • The type of the V2V conversion host must be consistent with that of the source cloud platform.
      • The V2V conversion host is a host in the specified destination cluster. Make sure that the hardware resources are sufficient for V2V migration.
      • If you select multiple source VM instances, note that the V2V jobs created accordingly will share the same V2V conversion host.
    • Source Host IP: Enter the IP address of the source host.
    • Source Host SSH Port: Set the SSH port of the source host. Default: 22.
    • SSH Username: Enter the username. Default: root.
    • SSH Password:
      • If you select Password, enter the SSH password. You can log in to the source host through the SSH password authentication.
      • If you select PrivKey, enter the corresponding SSH private key. You can log in to the source host through the SSH private key authentication.
        Note: Before you select this option, create an SSH private key for the source host in advance.
    • Virsh Info:
      • By default, this checkbox is not selected, indicating that the virtual resources of the source host are not remotely accessed through virsh.
      • If selected, you need to enter the SASL Username and SASL Password when the remote libvirtd requires Simple Authentication and Security Layer (SASL) authentication. You can securely connect to the remote libvirtd only after passing the verification.
        • SASL Username: Enter the corresponding SASL username.
        • SASL Password: Enter the corresponding SASL password.
    • Get Source VM Info: Obtain information about the running or paused VM instances that are available for migration.
    • Source VM: Select one or more KVM VM instances from the source host.
      Note:
      • You can select up to 50 VM instances at a time.
      • Do not power off the VM instances to be migrated.
      • If you select more than one VM instance, corresponding V2V jobs will be created in bulk. Note that one V2V job corresponds to one source VM instance.
    • Pause Running VM:
      • By default, this checkbox is not selected, indicating that the VM instances continue to run during the migration. This ensures the business continuity of the source VM instances.
      • If selected, the source VM instances will be paused when the migration starts, and the data written to the disk at that time will be migrated. After the migration is completed, you need to manually start the paused source VM instances.
      Note: For VM instances with high I/O, we recommend that you pause them before migration to ensure the data integrity.
    Figure 8. Configure Source Resources


  2. Configure the destination resources.
    Set the following parameters:
    • Destination Zone: By default, the current zone is displayed.
    • Destination Cluster: Select a destination cluster. Then, the estimated CPU usage and memory usage are displayed.
      • Estimated CPU usage: displays the number of the used CPUs of the source VM instance and the total number of available CPUs in the destination cluster.
      • Estimated memory usage: displays the used memory size of the source VM instance and the total available memory size in the destination cluster.
    • Destination Primary Storage: Select a destination primary storage. Then, the estimated primary storage usage is displayed.
      • Estimated storage usage: displays the used storage of the source VM instance and the total available storage of the destination primary storage.
    • Compression mode: Choose whether to enable the compression mode. By default, the compression mode is enabled.
      Note:
      • Enabling the compression mode compresses the caches of the migration data and improves the cache space utilization of the V2V conversion host.
      • If the destination primary storage is Ceph, we recommend that you do not use the compression mode.
    Figure 9. Configure Destination Resources


  3. Configure the network mapping.
    In this step, consider the following:
    • The source VM instance has a NIC attached.
    • The source VM instance does not have a NIC attached.
    1. If the source VM instance has a NIC attached,
      Set the following parameters:
      • Destination Network: Select a destination network as needed. The destination network is the network attached to the specified destination cluster.
    2. If the source VM instance does not have a NIC attached, go to the next step to manually configure the destination NIC.
    Figure 10. Configure Network Mapping


  4. Configure the destination VM instance.
    In this step, consider the following:
    • The VM instance has a NIC attached.
    • The VM instance does not have a NIC attached.
    1. If the source VM instance does not have a NIC attached,
      configure the destination VM instance by setting the following parameters:
      • Start VM After Migration: Choose whether to automatically start the destination VM instance after the migration.
      • VM Configuration: Select the VM instance to be configured. You can configure the VM instance by setting the following parameters.
        • Name: Set the name of the destination VM instance.
        • NIC: Configure the NIC information.
          • Network: Select the network for the destination VM instance.
          • IP Address: Optional. Configure the IP address of the destination NIC.
            Note: If not configured, the IP address of the destination NIC will be allocated by the system.
          • MAC Address: Optional. Configure the MAC address of the destination NIC.
            Note: If not configured, the MAC address of the destination NIC will be the same as that of the source NIC after migration.
      Note:
      • Go to the next step if no further modification is needed.
      • Before you migrate a VM instance to the current cloud, make sure that the VM instance has at least one NIC attached.
    2. If the VM instance has a NIC attached,
      configure the destination VM instance by setting the following parameters:
      • Start VM After Migration: Choose whether to automatically start the destination VM instance after the migration.
      • VM Configuration: Select the VM instance to be configured. You can configure the VM instance by setting the following parameters:
        • Name: Set the name of the destination VM instance.
        • CPU: Set the number of CPU cores for the destination VM instance. The number must be an integer ranging from 1 to 1024.
        • Memory: 16MB~100TB。: Set the memory size for the destination VM instance. The memory must be an integer ranging from 16 MB to 100 TB.
        • Platform: Select the image platform type.
          The image platform determines the platform used for creating VM instances. You can set whether to use KVM VirtIO drivers (including disk drivers and NIC drivers).
          • Linux: If VirtIO is enabled, the image operating system (OS) will have a VirtIO driver attached. If VirtIO is disabled, the OS, such as RHEL 5.8, will use a QEMU device instead.
          • Windows: If VirtIO is enabled, the image OS will have a VirtIO driver attached. If VirtIO is disabled, the OS will use a QEMU device instead.
          • Other: If VirtIO is enabled, the image OS will have a VirtIO driver attached. If VirtIO is disabled, the OS will use a QEMU device instead. This type of platform is compatible with some operating systems of earlier versions that do not support VirtIO drivers.
        • VirtIO: Choose whether to enable VirtIO based on your operating system and platform.
        • Volume: Select the volume to be migrated and set a name for the volume.
        • NIC: Configure the destination NIC information by setting the following parameters:
          • Network: Select the network for the destination VM instance.
          • Specify IP: Optional. Configure the IP address for the destination NIC.
            Note: If not configured, the IP address of the destination NIC will be allocated by the system.
          • MAC Address: Optional. Configure the MAC address for the destination NIC.
            Note: If not configured, the MAC address of the destination NIC will the same as that of the source NIC.
      Note: Before you migrate a VM instance to the current cloud, make sure that the VM instance has at least one NIC attached.
    Figure 11. Configure Destination VM


  5. Confirm and Submit.
    Figure 12. Confirm and Submit


Manage a V2V Job

On the main menu of ZStack Cloud, choose Platform O&M > Migration Service > V2V Migration. Then, the V2V Migration page is displayed.

The following table lists the actions that you can perform on a V2V job.
Action Description
Reboot V2V Job Reboot a V2V job if the job failed.
Note:
  • If migration data caches exist, rebooting the V2V job can improve the migration efficiency.
  • You can set the period for retaining the migration data caches in the global setting.
Edit V2V Job Modify the name and description of a V2V job.
Delete V2V Job Delete a V2V job after migration.

V2V Job Details

On the V2V Migration page, click on the name of a V2V job. Then, the details page of the V2V job is displayed. On the details page, you can view the V2V job status and the basic information about the source VM instance and destination VM instance.

Figure 13. V2V Job Details


V2V Conversion Host

Before you can perform V2V migration, specify a host in the destination cluster as the V2V conversion host.

Add a V2V Conversion Host

On the main menu of ZStack Cloud, choose Platform O&M > Migration Service > V2V Conversion Host. On the V2V Conversion Host page, click Add V2V Conversion Host. Then, the Add V2V Conversion Host page is displayed.

On the displayed page, set the following parameters:
  • Name: Enter a name for the V2V conversion host.

    Note that the name must be 1 to 128 characters in length and can contain Chinese characters, letters, digits, hyphens (-), underscores (_), periods (.), parenthesis (), colons (:), and plus signs (+).

  • Description: Optional. Enter a description for the V2V conversion host.
  • Type: Select a V2V conversion host type, including VMware and KVM.
    Note: The type of the V2V conversion host must be consistent with that of the source cloud platform.
  • Host: Select a host from the destination cluster as the V2V conversion host.
    Note: A host cannot be used as a V2V conversion host for both the VMware platform type and the KVM platform type at the same time.
  • Cache Path: Enter a local path on the V2V conversion host as the storage path.
    Note: During the V2V migration, the VM system and data are first cached in the V2V conversion host and then imported into the target primary storage.
  • Migration Network: Optional. If you deployed an independent network for V2V migration, enter the CIDR of the network.
    Note:
    • If you deployed an independent network for V2V migration, you could add the network to the Cloud directly.
    • In a V2V migration scenario, the migration network is used to convert data migrated from the destination primary storage to the V2V conversion host.
    • Using an independent migration network can avoid network congestion and improve transmission efficiencies.
    • If not set, the management network will be used by default for V2V migration.
  • Upstream Bandwidth: Optional. Set the upstream bandwidth of the V2V conversion host. This parameter limits the speed of uploading data from the V2V conversion host to the destination primary storage. The upstream bandwidth must be an integer ranging from 1 Mbps to 32 Gbps. Unit: Mbps and Gbps.
  • Downstream Bandwidth: Optional. Set the downstream bandwidth for the V2V conversion host. This parameter limits the speed of downloading data from the source primary storage to the V2V conversion host. The downstream bandwidth must be an integer ranging from 1 Mbps to 32 Gbps. Unit: Mbps and Gbps.

V2V Conversion Host Details

On the main menu of ZStack Cloud, choose Platform O&M > Migration Service > V2V Conversion Host. On the V2V Conversion Host page, click on the name of a V2V conversion to go to the details page. The details page displays the basic information, monitoring data, and configurations of the V2V conversion host.

Figure 14. V2V Conversion Host Details


Manage a V2V Conversion Host

On the main menu of ZStack Cloud, choose Platform O&M > Migration Service > V2V Conversion Host. Then, the V2V Conversion Host page is displayed.

The following table lists the actions that you can perform on a V2V conversion host.
Action Description
Edit V2V Conversion Host Modify the name and description of the V2V conversion host.
Enable V2V Conversion Host Enable a V2V conversion host.
Disable V2V Conversion Host Disable a V2V Conversion host.
Note: If you disable a V2V conversion host when you perform a V2V job, the job is not affected.
Set Network Bandwidth Set the upstream or downstream bandwidth of the V2V conversion host.
Delete V2V Conversion Host Delete a V2V conversion host.
Note:
  • Deleting a V2V conversion host automatically cancels the ongoing V2V job.
  • Deleting a V2V conversion host also deletes the local records of the backup data on the conversion host, but the actual data is not affected. If you add this conversion host again, the local records are not recovered automatically.

Considerations

  • A V2V conversion host must have sufficient hardware resources, such as network bandwidth and disk space. The following table lists the minimum configuration requirements.
    Hardware Configuration Requirements
    CPU Minimum 8 cores
    Memory Minimum 16 GB
    Network Minimum 1 Gigabyte NIC
    Storage Minimum 50 GB for the rest of storage spaces
    Note: You can modify the storage configuration according to the number of VM instances to be migrated.
  • The type of the V2V conversion host must be consistent with that of the source cloud platform.
  • You can set an independent migration network and a network QoS for a V2V conversion host to control transmission bottlenecks and to improve migration efficiencies.

Typical Practices

Source Cloud Platform: VMware

About this task

Scenario: Due to business needs, you need to migrate VM instances from your vCenter to the current cloud. Assume that:
  • You deployed a vCenter environment and the latest ZStack Cloud Private Cloud and took over vCenter on ZStack Cloud Private Cloud.
  • You prepared a storage server and added it to the destination cluster as a compute node. You use this compute node as the V2V conversion host.
  • You purchased and installed the Migration Service module.
The following table lists the information about the source and the destination cloud platform.
Source Cloud Platform Destination Cloud Platform
vCenter
  • Version: 6.0
  • Primary storage type: LocalStorage
  • Network: public network, flat network, and VPC network
  • Number of VM instances: 4
    • VM-1-centos7 (with 1 data volume)
    • VM-2-win2008 (with 2 data volumes)
    • VM-3-win2016 (with 1 data volume)
    • VM-4-win2012 (with 2 data volumes)
 ZStack Cloud Private Cloud
  • Version: the latest version
  • Primary storage type: SharedBlock
  • Network: public network, flat network, and VPC network
The workflow is as follows:
  1. Add a V2V conversion host.
  2. Create a V2V job to migrate the 4 VM instances from the vCenter that you took over to the current cloud.

Procedure

  1. Add a V2V conversion host.

    In this scenario, you will add a compute node prepared in the destination cluster as the V2V conversion host.

    On the main menu of ZStack Cloud, choose Platform O&M > Migration Service > V2V Conversion Host. On the V2V Conversion Host page, click Add V2V Conversion Host. Then, the Add V2V Conversion Host page is displayed.

    On the displayed page, set the following parameters:
    • Name: Enter a name for the V2V conversion host.
    • Description: Optional. Enter a description for the V2V conversion host.
    • Type: Select VMware Platform.
      Note: The type of the V2V conversion host must be consistent with that of the source platform you selected when you create a V2V job.
    • Host: Select a host from the destination cluster as the V2V conversion host.
      Note: A host cannot be used as a V2V conversion host for both the VMware platform type and the KVM platform type at the same time.
    • Cache Path: Enter a local path on the V2V conversion host as the storage path.
      Note: During the V2V migration, the VM system and data are first cached in the V2V conversion host and then imported into the target primary storage.
    • Migration Network: Optional. If you deployed an independent network for V2V migration, enter the CIDR of the network.
      Note:
      • If you deployed an independent network for V2V migration, you could add the network to the Cloud directly.
      • In a V2V migration scenario, the migration network is used to convert data migrated from the destination primary storage to the V2V conversion host.
      • Using an independent migration network can avoid network congestion and improve transmission efficiencies.
      • If not set, the management network will be used by default for V2V migration.
    • Upstream Bandwidth: Optional. Set the upstream bandwidth of the V2V conversion host. This parameter limits the speed of uploading data from the V2V conversion host to the destination primary storage. The upstream bandwidth must be an integer ranging from 1 Mbps to 32 Gbps. Unit: Mbps and Gbps.
    • Downstream Bandwidth: Optional. Set the downstream bandwidth for the V2V conversion host. This parameter limits the speed of downloading data from the source primary storage to the V2V conversion host. The downstream bandwidth must be an integer ranging from 1 Mbps to 32 Gbps. Unit: Mbps and Gbps.
    Figure 15. Add V2V Conversion Host


  2. Create a V2V job to migrate these 4 VM instances from the vCenter that you took over to the current cloud.

    On the main menu of ZStack Cloud, choose Platform O&M > Migration Service > V2V Migration. On the V2V Migration page, click Create V2V Job.Then, the Create V2V Job page is displayed

    1. Configure the source resources.
      Set the following parameters:
      • Name: Enter a name for the V2V job.

        The name must be 1 to 128 characters in length and can contain Chinese characters, letters, digits, spaces, hyphens (-), underscores (_), periods (.), parenthesis (), colons (:), and plus signs (+) and cannot begin or end with spaces.

      • Description: Optional. Enter a description for the V2V job.
      • Source Platform: Select the source platform type. Here, select VMware.
      • V2V Conversion Host: Select a V2V conversion host.
        Note:
        • Before you can create a V2V job, add a V2V conversion host to the Cloud.
        • The type of the V2V conversion host must be consistent with that of the source cloud platform.
        • The V2V conversion host is a host in the specified destination cluster. Make sure that the hardware resources are sufficient for V2V migration.
        • If you select multiple source VM instances, note that the V2V jobs created accordingly will share the same V2V conversion host.
      • Source Cluster: Select a cluster from the vCenter that you took over as the source cluster.
      • Source VM: Select one or more vCenter VM instances from the source cluster as the source VM instance or VM instances. You can select up to 50 VM instances at a time.
        Note:
        • If you select more than one VM instance, corresponding V2V jobs will be created in bulk. Note that one V2V job corresponds to one source VM instance.
        • For Windows Server 2012 R2 and Windows Server 2016 VM instances, you need to manually disable the hibernation feature and shut down these VM instances before you create V2V jobs.
          To disable or enable the Windows hibernation feature, run the following commands:
          • Disable Windows hibernation: cmd-->“powercfg -h off”
          • Enable Windows hibernation: cmd-->“powercfg -h on”
        • If one of the source VM instances has a data volume, make sure that the disk mode of the data volume is Dependent. Otherwise, the V2V job might fail.
      Figure 16. Configure Source Resources


    2. Configure destination resources.
      Set the following parameters:
      • Destination Zone: By default, the current zone is displayed.
      • Destination Cluster: Select a destination cluster. Then, the estimated CPU usage and memory usage are displayed.
        • Estimated CPU usage: displays the number of the used CPUs of the source VM instance and the total number of available CPUs in the destination cluster.
        • Estimated memory usage: displays the used memory size of the source VM instance and the total available memory size in the destination cluster.
      • Destination Primary Storage: Select a destination primary storage. Then, the estimated primary storage usage is displayed.
        • Estimated storage usage: displays the used storage of the source VM instance and the total available storage of the destination primary storage.
      • Compression mode: Choose whether to enable the compression mode. By default, the compression mode is enabled.
        Note:
        • Enabling the compression mode compresses the caches of the migration data and improves the cache space utilization of the V2V conversion host.
        • If the destination primary storage is Ceph, we recommend that you do not use the compression mode.
      Figure 17. Configure Destination Resources


    3. Configure network mapping.

      In this scenario, all the chosen VM instances have a NIC attached.

      Set the following parameters:
      • Destination Network: Select a destination network as needed. The destination network is the network attached to the specified destination cluster.
      Figure 18. Configure Network Mapping | Source VMs Have NIC Attached


    4. Configure destination VM instances.

      Parameters of the destination VM instances are configured by the system by default. Therefore, go to the next step if no further modification is needed.

      You can also configure the destination VM instances by setting the following parameters:
      • Start VM After Migration: Choose whether to automatically start the destination VM instance after the migration.
      • Use Source MAC and IP: Choose whether to use the source MAC and IP addresses. By default, these addresses are not used.
        Note:
        • If not used, you can customize the MAC and IP addresses for the destination NIC. If you do configure them, the destination MAC address will be the same as the source MAC address after migration, and the IP address of the destination NIC will be allocated by the system.
        • If used, the destination NIC will use the MAC and IP addresses of the source NIC in the next step. If the source NIC does not have an IP address, the IP address of the destination NIC will be allocated by the system.
      • VM Configuration: Select the VM instance to be configured. You can configure the VM instance by setting the following parameters:
        • Name: Set the name of the destination VM instance.
        • NIC: Configure the NIC information.
          • Network: Select the network for the destination VM instance.
          • IP Address: Optional. Configure the IP address of the destination NIC.
            Note: If not configured, the IP address of the destination NIC will be allocated by the system.
          • MAC Address: Optional. Configure the MAC address of the destination NIC.
            Note: If not configured, the MAC address of the destination NIC will be the same as that of the source NIC after migration.
      • Boot Partition: If the VM instance to be migrated has multiple boot partitions, specify one as the root volume for the VM instance.
      Figure 19. Configure Destination VMs / VMs Have NIC Attached


    5. Confirm and submit.

      Confirm the information about the V2V job. You can modify the information by clicking the Edit icon next to each step.

      Figure 20. Confirm and Submit




What to do next

So far, we introduced the VMware-based V2V migration practice.

Source Cloud Platform: KVM

About this task

Scenario: Due to business needs, you need to migrate VM instances from your KVM cloud platform to the current cloud. Assume that:
  • You deployed a KVM-based open-source cloud platform and the latest ZStack Cloud Private Cloud.
  • You prepared a storage server and added it to the destination cluster as a compute node. You use this compute node as the V2V conversion host.
  • You purchased and installed the Migration Service module.
The following table lists the information about the source and the destination cloud platform.
Source Cloud Platform Destination Cloud Platform
An open-source, KVM-based cloud platform
  • Primary storage type: SAN storage
  • Number of appliance VMs: 4
 ZStack Cloud Private Cloud
  • Version: the latest version
  • Primary storage type: SharedBlock
  • Network: public network
The workflow is as follows:
  1. Add a V2V conversion host.
  2. Create a V2V job to migrate the 4 VM instances from the KVM cloud platform to the current cloud.

Procedure

  1. Add a V2V conversion host.

    In this scenario, you will add a compute node prepared in the destination cluster as the V2V conversion host.

    On the main menu of ZStack Cloud, choose Platform O&M > Migration Service > V2V Conversion Host. On the V2V Conversion Host page, click Add V2V Conversion Host. Then, the Add V2V Conversion Host page is displayed.

    On the displayed page, set the following parameters:
    • Name: Enter a name for the V2V conversion host.
    • Description: Optional. Enter a description for the V2V conversion host.
    • Type: Select KVM Platform.
      Note: The type of the V2V conversion host must be consistent with that of the source platform you selected when you create a V2V job.
    • Host: Select a host from the destination cluster as the V2V conversion host.
      Note: A host cannot be used as a V2V conversion host for both the VMware platform type and the KVM platform type at the same time.
    • Cache Path: Enter a local path on the V2V conversion host as the storage path.
      Note: During the V2V migration, the VM system and data are first cached in the V2V conversion host and then imported into the target primary storage.
    • Migration Network: Optional. If you deployed an independent network for V2V migration, enter the CIDR of the network.
      Note:
      • If you deployed an independent network for V2V migration, you could add the network to the Cloud directly.
      • In a V2V migration scenario, the migration network is used to convert data migrated from the destination primary storage to the V2V conversion host.
      • Using an independent migration network can avoid network congestion and improve transmission efficiencies.
      • If not set, the management network will be used by default for V2V migration.
    • Upstream Bandwidth: Optional. Set the upstream bandwidth of the V2V conversion host. This parameter limits the speed of uploading data from the V2V conversion host to the destination primary storage. The upstream bandwidth must be an integer ranging from 1 Mbps to 32 Gbps. Unit: Mbps and Gbps.
    • Downstream Bandwidth: Optional. Set the downstream bandwidth for the V2V conversion host. This parameter limits the speed of downloading data from the source primary storage to the V2V conversion host. The downstream bandwidth must be an integer ranging from 1 Mbps to 32 Gbps. Unit: Mbps and Gbps.
    Figure 21. Add V2V Conversion Host


  2. Create a V2V migration job to migrate 4 KVM instances from the source cloud platform to the current cloud.

    On the main menu of ZStack Cloud, choose Platform O&M > Migration Service > V2V Migration. On the V2V Migration page, click Create V2V Job.Then, the Create V2V Job page is displayed

    1. Configure the source resources.
      Set the following parameters:
      • Name: Enter a name for the V2V job.
      • Description: Optional. Enter a description for the V2V job.
      • Source Platform: Select KVM.
      • V2V Conversion Host: Select a V2V conversion host of the KVM type you added before.
      • Source Host IP: Enter the IP address of the source host.
      • Source Host SSH Port: Set the SSH port of the source host. Default: 22.
      • SSH Username: Enter the username. Default: root.
      • SSH Password: Enter the corresponding SSH password.
      • Virsh Info: If not selected, the virtual resources of the source host are not remotely accessed through virsh.
      • Source VM Info: Obtain information about the running or paused VM instances that are available for migration.
      • Source VM: Select four KVM instances from the source host.
        Note:
        • Do not power off the VM instances to be migrated.
        • If you select more than one VM instance, corresponding V2V jobs will be created in bulk. Note that one V2V job corresponds to one source VM instance.
      • Pause VM: If selected, the source VM instances will be paused when a V2V job starts.
      Figure 22. Configure Source Resources


    2. Configure the destination resources.
      Set the following parameters:
      • Destination Zone: By default, the current zone is displayed.
      • Destination Cluster: Select a destination cluster. Then, the estimated CPU usage and memory usage are displayed.
        • Estimated CPU usage: displays the number of the used CPUs of the source VM instance and the total number of available CPUs in the destination cluster.
        • Estimated memory usage: displays the used memory size of the source VM instance and the total available memory size in the destination cluster.
      • Destination Primary Storage: Select a destination primary storage. Then, the estimated primary storage usage is displayed.
        • Estimated storage usage: displays the used storage of the source VM instance and the total available storage of the destination primary storage.
      • Compression mode: Choose whether to enable the compression mode. By default, the compression mode is enabled.
        Note:
        • Enabling the compression mode compresses the caches of the migration data and improves the cache space utilization of the V2V conversion host.
        • If the destination primary storage is Ceph, we recommend that you do not use the compression mode.
      Figure 23. Configure Destination Resources


    3. Configure the network mapping.

      In this scenario, a chosen VM instance does not have a NIC attached.

      1. For the source VM instance that has a NIC attached,
        Set the following parameters:
        • Destination Network: Select a destination network as needed. The destination network is the network attached to the specified destination cluster.
      2. For the source VM instance that does not have a NIC attached,

        Go to the next step to manually configure the destination NIC.

      Figure 24. Configure Network Mapping


    4. Configure destination VM instances.
      configure the destination VM instance by setting the following parameters:
      • Start VM After Migration: Choose whether to automatically start the destination VM instance after the migration.
      • VM Configuration: Select the VM instance to be configured. You can configure the VM instance by setting the following parameters:
        • Name: Set the name of the destination VM instance.
        • NIC: Configure the NIC information.
          • Network: Select the network for the destination VM instance.
          • IP Address: Optional. Configure the IP address of the destination NIC.
          • Note: If not configured, the IP address of the destination NIC will be allocated by the system.
          • MAC Address: Optional. Configure the MAC address of the destination NIC.
            Note: If not configured, the MAC address of the destination NIC will be the same as that of the source NIC after migration.
        • Boot Partition: If the VM instance to be migrated has multiple boot partitions, specify one as the root volume for the VM instance.
      Note: Before you migrate a VM instance to the current cloud, make sure that the VM instance has at least one NIC attached.
      Figure 25. Configure Destination VMs


    1. Confirm and submit.

      Confirm the information about the V2V job. You can modify the information by clicking the Edit icon next to each step.

      Figure 26. Confirm and Submit




What to do next

So far, we introduced the KVM-based V2V migration practice.
PreviousAlibaba Cloud Hybrid Cloud TutorialNextVPC Network Tutorial
V2V Migration Tutorial | 5.4.12 | ZStack Cloud · ZCF | ZStack Resource Center