Migrating a VM Image

Prerequisites

• You have logged in to the Kunpeng DevKit.
• You have prepared the migration source components. For details, see Preparing Migration Source Components.

Important Notes

• After a migration task is complete on a node, you can create another migration task on the node.
• If a node is occupied by another project, wait until the occupied project is complete and the node is automatically released. Alternatively, delete the project and select another node.
• Components on the same node cannot be migrated to the same target components.

Procedure

1. Click System Migration in the navigation tree on the left and then click to go to the New Project tab page.
   Figure 1 Basic Settings
   
2. Set Migration Project Name. A project name is automatically generated by default, which can be changed if needed.

   The name must meet the following requirements:

   • Can contain only letters, digits, and underscores (_).
   • 1 to 64 characters.
3. Select VM image migration for Migration Scenario.
4. Select migration project nodes. You can select a maximum of 20 nodes and search for nodes by their IP addresses or names. If a node is not included on the list, you can click Add Node to add it for the migration project. For details, see Managing Agent.
5. Click Collect Source Component to collect component information about the migration project nodes. The collection progress is displayed.
6. After the collection is complete, the Configure Migration Components area is displayed. Configure Component Table.
   Figure 2 Configure Migration Components
   

   Table 1 Component Table

   Parameter	Description
   Source Component Name	Name of the source component to be migrated.
   Owning Node	Node to which the component belongs.
   Origin of Source Component	Indicates where the source component comes.
   Target Component Name	Name of the target component.
   Origin of Target Component	For middleware and databases, you need to configure where the target component comes. The options are: Download from URL: By default, the target component package is downloaded from the Kunpeng image repository and automatically installed. Obtain from node server: Obtain the target component package from the specified path on the node and start an automatic installation. Access the Kunpeng mirror site to obtain the component installation package. Log in to the tool through SSH and upload the installation package to a user-defined directory on the node server. Specify the installation package path as the target component path. Upload target component package: Click Origin of Target Component in the lower part of the dialog box to obtain the target component package.
   Default Deployment Path	The default deployment path of the target component cannot be modified. NOTE: The tool deploys the target component based on the source component path. If the source component path cannot be determined, the default deployment path is used. For the detailed deployment path, see the suggestions on the migration result page.
   Commercial Certificate	Commercial software requires a license file. Click Upload to upload the required license file.
   Operation	You can add, edit, and delete components in Component Table. Click Add, enter correct component information, and click OK. Click Edit, modify and check component information, and click OK. Click Delete to delete necessary components. Then click OK.

   

   • When configuring the components to be migrated, you can click Save Configuration in the lower left corner to save the current configuration.
   • The estimated migration duration is displayed in real time based on the selected migration content. You can adjust your migration plan accordingly.
   • In the upper part of Component Table, you can click Add Component Information and enter the information about the component to be added.

   To manually add component information, click Add Component Information above the table. See Figure 3. The source component (middleware or application) can come from any of the following origins:

   Figure 3 Add Component Information
   
   

   For details about how to package source components (except the RabbitMQ middleware), see Preparing Migration Source Components.

   • Obtain from node server: Obtain the source component package from the specified path on the owning node, scan and analyze it, and generate a migration guide report. If the component belongs to middleware, perform the following steps:
     1. Compress the installation directory of the source component to be scanned into a package, for example, a tar.gz package. Replace the example package name and source component directory with the actual ones.

        1	tar cvf xxx.tar.gz /xxx/xxx/xxx

     2. Log in to the tool through SSH and upload the compressed package to a user-defined directory on the node server.
     3. Go to the directory of storing the compressed package.

        1	cd User-defined_directory

     4. Decompress the source component package. Replace the example package name with the actual one.

        1	tar xvf xxx.tar.gz

     5. After the decompression is complete, you can run the following command to delete the source component package.

        1	rm -f xxx.tar.gz

     6. Set the path to the decompressed file as the source component path.
   • Upload source component package: Upload the source component package, scan and analyze it, and generate a migration guide report. If the component belongs to middleware, perform the following steps:
     1. Compress the directory of the source component to be scanned into a package, for example, a tar.gz package. Replace the example package name and source component directory with the actual ones.

        1	tar cvf xxx.tar.gz /xxx/xxx/xxx

     2. Upload the source component package.
   • No source component available: No source component package is provided and no migration analysis is performed. This parameter is available only to middleware.
7. Trust Target Component URL: If you have selected Download from URL, choose whether to trust the target component URL.

   If you enable Trust Target Component URL, SSL certificate verification will be skipped for all software downloads in this migration task. Check that the URL is secure.

8. Click Start Migration.