ZStack 3.10.0>Tutorials>Advanced Features>V2V Migration Tutorial>Example Application Scenario

Example Application Scenario

Source Cloud Platform: VMware

Assume that you deployed a vCenter environment and the latest ZStack Private Cloud, and took over vCenter in ZStack Private Cloud. Due to business needs, you need to migrate VM instances from your vCenter to the current cloud.

Assume that you have purchased and installed the Migration Service module.

Before V2V migration, you need to specify a host in the destination cluster as the V2V conversion host. In this scenario, assume that you have prepared a storage server in advance and added the storage server to the destination cluster as a compute node. You use this compute node as the V2V conversion host.

The following table lists the information about the source cloud platform and the destination cloud platform.

Source Cloud Platform	Destination Cloud Platform
vCenter Version: 6.0 Primary storage type: LocalStorage Network: public network and private network (flat network and vRouter network) Number of appliance VMs: 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 Private Cloud Version: the latest version Primary storage type: SharedBlock Network: public network and private network (flat network, vRouter 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.
In the navigation pane of the ZStack Private Cloud UI, choose Advanced Function > Migration Service > V2V Conversion Host. On the V2V Conversion Host page, click Add V2V Conversion Host. On the displayed Add V2V Conversion Host 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.
- Host: Select a compute node you prepared before from the destination cluster as the V2V conversion host.
- Storage Path: Enter a local path on the V2V conversion host as the storage path.
- Migration Network: Optional. If you deployed an independent network for V2V migration, enter the CIDR of the network.
- Upstream Bandwidth: Optional. Set the upstream bandwidth of the V2V conversion host.
- Downstream Bandwidth: Optional. Set the downstream bandwidth of the V2V conversion host.
As shown in Figure 1.
Figure 1. Add V2V Conversion Host
Create a V2V job to migrate the 4 VM instances from the vCenter that you took over to the current cloud.

In the navigation pane of the ZStack Private Cloud UI, choose Advanced Function > Migration Service > V2V Job. On the V2V Job page, click Create V2V Job. Then, the Create V2V Job page is displayed.
1. Configure the source resources.
  Set the following parameters:
  - Source Platform: Select VMware.
  - Name: Enter a name for the V2V job.
  - Description: Optional. Enter a description for the V2V job.
  - V2V Conversion Host: Select a V2V conversion host of the VMware type you added before.
  - Source Cluster: Select a source vCenter cluster.
  - Source VM: Select four vCenter VM instances from the source cluster you selected in the preceding step.
    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 the VM instances before you create a V2V job.
    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.
    As shown in Figure 2.
    Figure 2. Disk Mode: Dependent
  As shown in Figure 3.
  Figure 3. 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. After selected, the estimated CPU usage and memory usage are displayed.
  - Destination Primary Storage: Select a destination primary storage. After selected, the estimated primary storage usage is displayed.
  - Compression mode: Select this checkbox.
  As shown in Figure 4.
  Figure 4. Configure Destination Resources
3. Configure network mapping.
  In this scenario, all the chosen VM instances have a NIC attached.
  Configure each network mapping as follows:
  - Network mapping:
    
    Source network: The source vCenter network is displayed.
    
    IP usage: The estimated IP usage of the source network.
    
    Destination network: Select a corresponding destination network as needed. The destination network is the network attached to the specified destination cluster.
  - Use IP and MAC of source VM: Do not select this checkbox and go to the next step instead. In the next step, you can customize the MAC address and IP address for the destination NIC. If you do not configure them, the destination NIC MAC address will be the same as the source NIC MAC address after migration, and the IP address of the destination NIC will be allocated by the system.
  As shown in Figure 5.
  Figure 5. Configure Network Mapping | All Source VMs Have a NIC Attached
4. Configure destination VM instances.
  Go to the next step if no further modification is needed. Parameters of the destination VM instances are configured by the system by default.
  You can also configure the destination VM instances by setting the following parameters:
  - Auto start VM after V2V migration: By default, this checkbox is selected, indicating that the destination VM instances will be automatically started after migration.
  - Destination VM Info:
    
    Name: Set the name of the destination VM instance.
  - Source NIC No.: The NIC No. of the source VM instance is displayed.
  - Source NIC Info: The NIC information about the source VM instance, including the source network, MAC address, and IP address, is displayed.
  - Destination NIC Info:
    
    L3 Network: Select an L3 network used by the destination VM instance.
    
    MAC Address: Optional. You can manually configure the MAC address of the destination NIC. If not configured, the MAC address of the destination NIC will be the same as that of the source NIC after migration.
    
    IP Address: Optional. You can manually configure the IP address of the destination NIC. If not configured, the IP address of the destination NIC will be allocated by the system.
    
    Note:
    
    Before you migrate a VM instance to the current Cloud, make sure that the VM instance has at least one NIC attached.
    
    You can manually configure the MAC address and IP address for the destination NIC, or let the system configure them automatically.
    
    Manual configuration: You can use the MAC address and IP address of the source NIC as the destination MAC address and IP address, respectively.
    
    Auto configuration: After migration, the MAC address of the destination NIC is the same as that of the source NIC, and the IP address of the destination NIC is allocated by the system.
  As shown in Figure 6.
  Figure 6. Configure Destination VMs | All Source VMs Have a 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.
  As shown in Figure 7.
  Figure 7. Confirm and Submit
The chosen four vCenter VM instances are successfully migrated to the current cloud.
As shown in Figure 8.
Figure 8. List of V2V Jobs

Source Cloud Platform: KVM

Assume that you deployed an open source, KVM-based cloud environment and the latest ZStack Private Cloud. Due to business needs, you need to migrate VM instances from your KVM cloud platform to the current cloud

Assume that you have purchased and installed the Migration Service module.

The following table lists the information about the source cloud platform 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 VM-1-CentOS7 (without disk volumes) VM-2-Win2012 (without disk volumes) VM-3-Win2016 (with 1 disk volume) VM-4-Ubuntu18 (without disk volumes)	ZStack Private Cloud Version: the latest version Primary storage type: SharedBlock Network: private network (flat network and vRouter network)

The workflow is as follows:

Add a conversion host.
Create a V2V migration job to migrate 4 KVM instances from the source 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.
In the navigation pane of the ZStack Private Cloud UI, choose Advanced Function > Migration Service > V2V Conversion Host. On the V2V Conversion Host page, click Add V2V Conversion Host. On the displayed Add V2V Conversion Host 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.
- Host: Select a compute node you prepared before from the destination cluster as the V2V conversion host.
- Storage Path: Enter a local path on the V2V conversion host as the storage path.
- Migration Network: Optional. Optional. If you deployed an independent network for V2V migration, enter the CIDR of the network.
- Upstream Bandwidth: Optional. Set the upstream bandwidth of the V2V conversion host.
- Downstream Bandwidth: Optional. Set the downstream bandwidth of the V2V conversion host.
As shown in Add V2V Conversion Host.
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.

In the navigation pane of the ZStack Private Cloud UI, choose Advanced Function > Migration Service > V2V Job. On the V2V Job page, click Create V2V Job. Then, the Create V2V Job page is displayed.
1. Configure the source resources.
  Set the following parameters:
  - Source Platform: Select KVM.
  - Name: Enter a name for the V2V job.
  - Description: Optional. Enter a description for the V2V job.
  - V2V Conversion Host: Select a V2V conversion host of the KVM type you added before.
  - Configure Source Platform:
    
    Source Host IP: Enter the IP address of the source host.
    
    Source Host SSH Port: Set the SSH port of the source host. Default port: 22.
    
    SSH User Name: The default user name is root. You can also enter a normal user name.
    
    Password Type: Select Password.
    
    SSH Password: Enter the corresponding SSH password. You can log in to the source host through the SSH password authentication.
    
    Configure virsh: Do not select the checkbox. Then, the virtual resources of the source host are not remotely accessed through virsh.
  - Select Source VM:
    
    Get VM information: 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 accordingly in bulk. Note that one V2V job corresponds to one source VM instance.
    
    Pause running VMs: Select this checkbox. Then, the source VM instances will be paused when a V2V job starts.
  As shown in Figure 2.
  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. After selected, the available CPUs and memory in the destination cluster are displayed.
  - Destination Primary Storage: Select a destination primary storage. After selected, the available storage of the primary storage is displayed.
  - Compression mode: Select this checkbox.
  As shown in Figure 3.
  Figure 3. Configure Destination Resources
3. Configure network mapping.
  In this scenario, a chosen VM instance does not have a NIC attached.
  1. For source VM instances that have a NIC attached,
    Configure each network mapping as follows:
    
    Network mapping:
    
    Source NIC: The information about the source NIC is displayed.
    
    IP usage: The estimated IP usage of the source NIC.
    
    Destination network: Select a corresponding 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.
  As shown in Figure 4.
  Figure 4. Configure Network Mapping
4. Configure destination VM instances.
  1. For source VM instances that have a NIC attached,
    Configure the destination VM instances by setting the following parameters:
    
    Auto start VM after V2V migration: By default, this checkbox is selected, indicating that the destination VM instances will be automatically started after migration.
    
    Destination VM Info:
    
    Name: Set the name of the destination VM instance.
    
    CPU Core Count: Set the number of CPU cores for the destination VM instance.
    
    Memory: Set the memory capacity for the destination VM instance.
    
    Platform: Select an operating system type for the destination VM instance.
    
    Destination Data Volume Info:
    
    Root Volume Info: Set a display name for the root volume of the destination VM instance.
    
    Size (Root Volume): The root volume capacity of the destination VM instance is displayed.
    
    Data Volume Info: Set a display name for the data volume of the destination VM instance.
    
    Size (Data Volume): The data volume capacity of the destination VM instance is displayed.
    
    Note:
    
    By default, the root volume of a source VM instance is migrated.
    
    If a source VM instance has multiple data volumes attached, you can select one or more data volume to migrate.
    
    You can change the display name of a data volume migrated to the current cloud. However, you cannot change its real name that is used for distinguishing itself from others.
    
    Destination NIC Info:
    
    L3 Network: Select an L3 network used by the destination VM instance.
    
    VM NIC Setting:
    
    Fixed IP: Optional. You can manually configure the IP address of the destination NIC. If not configured, the IP address of the destination NIC will be allocated by the system.
    
    MAC Address: Optional. You can manually configure the MAC address of the destination NIC. If not configured, the MAC address of the destination NIC will be the same as that of the source NIC after migration.
    
    Note:
    
    Before you migrate a VM instance to the current cloud, make sure that the VM instance has at least one NIC attached.
    
    You can manually configure the MAC address and IP address for the destination NIC, or let the system to configure them automatically.
    
    Manual configuration: You can use the MAC address and IP address of the source NIC as the destination MAC address and IP address, respectively.
    
    Auto configuration: After migration, the MAC address of the destination NIC is the same as that of the source NIC, and the IP address of the destination NIC is allocated by the system.
  2. For the source VM instance that does not have a NIC attached,
    If No network is displayed next to the name of the source VM instance, you must manually configure the corresponding destination NIC.
    To configure the destination NIC, set the following parameters:
    
    Destination NIC Info:
    
    L3 Network: Select an L3 network used by the destination VM instance.
    
    VM NIC Setting:
    
    Fixed IP: Optional. You can manually configure the IP address of the destination NIC. If not configured, the IP address of the destination NIC will be allocated by the system.
    
    MAC Address: Optional. You can manually configure the MAC address of the destination NIC. If not configured, the MAC address of the destination NIC will be allocated by the system.
  As shown in Figure 5.
  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.
  As shown in Figure 6.
  Figure 6. Confirm and Submit
Migrate 4 KVM instances from the source platform to the current cloud, as shown in V2V Migration Job Page

Figure 7. V2V Migration Job Page