ZStack Cloud 4.4.0>Tutorials>Advanced Features>V2V Migration Tutorial>Typical Practices

Typical Practices

Source Cloud Platform: VMware

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:

Add a V2V conversion host.
Create a V2V job to migrate the 4 VM instances from the vCenter that you took over to the current cloud.

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 1. Add V2V Conversion Host
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 V2V job 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 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 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 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 4. 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 5. 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 6. Confirm and Submit

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

Source Cloud Platform: KVM

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:

Add a V2V conversion host.
Create a V2V job to migrate the 4 VM instances from the KVM cloud platform to the current cloud.

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 1. Add V2V Conversion Host
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 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 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 4. 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 5. 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 6. Confirm and Submit

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

Next Chapter:Glossary