Creating a Project

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

• A node that is being used by a project cannot be added again. You need to delete the project before adding the node.
• Components on the same node cannot be migrated to repetitive migration targets.

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 Creating a project
   
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 the nodes to be migrated. Click the Nodes to Migrate drop-down list and select target nodes from the drop-down list. You can select a maximum of 20 nodes at a time and search for nodes by their IP addresses.

   If no node information exists, click Add Node to add nodes.

   • Batch import information about multiple nodes using a template.
     1. In the Batch Import Node dialog box, click template table to obtain the template and enter node information.
        Figure 2 Batch Import Node
        
     2. After entering the node information, click Select File and confirm the SSH Transmission Note. Use the selected file to batch import nodes.
        Figure 3 SSH Transmission Note
        
   • Add information about a single node.

     In the Add Node dialog box, set parameters based on Table 1 and click OK.

     Figure 4 Adding a single node
     
     

     If you failed to add a node as a common user, run the usermod -G wheel userName command to add the common user to the wheel group.

     Table 1 Parameters for adding a node

     Parameter	Description
     (Optional) Node Name	Name of the node to be added. It is Node plus the node ID by default. The name must meet the following requirements: Can contain only letters, digits, and special characters (including @#$ %^&*()[]<>._-!-+ and spaces). 1 to 32 characters.
     (Optional) Installation Path	Absolute path where the node is installed. The default value is /opt. NOTE: The entered path cannot be /home. If the entered path belongs to the root user group, common users must have the read (r) and execute (x) permissions on the paths of all levels. If the entered path belongs to the devkit user group, user devkit must have the read (r) and execute (x) permissions on the paths of all levels.
     SSH Transmission Note	Certificate management uses the default SSH transmission channel of the server. To ensure data security and integrity, you are advised to use a secure SSH service, such as a secure SSH version configured with a secure encryption algorithm.
     Node IP Address	IP address of the server where the node is to be installed.
     Port	SSH port of the server where the node is to be installed. The default value is 22. The value ranges from 1 to 65535.
     User Name	User name for logging in to the node server. The default value is root. NOTE: To ensure SSH channel security, it is recommended that you log in as a common user.
     Authentication Mode	Authentication mode. The options are: Password authentication Key authentication NOTE: If you select Key authentication, you need to set SSH authentication information on the server where the Kunpeng DevKit is installed.
     Password	Password for logging in to the node server. NOTE: This parameter is displayed when Authentication Mode is set to Password authentication. If the node is installed by the root user, you need to enter the password of the root user. If the node is installed by a common user, you need to enter the passwords of both the common user and root user.
     Private Key File	Absolute path of the SSH private key file, for example, /home/devkit/id_rsa, for logging in to the node server. This parameter is displayed when Authentication Mode is set to Key authentication.
     (Optional) Passphrase	Password of the SSH private key file for logging in to the node server. If the SSH private key password is not configured, you do not need to set this parameter. This parameter is displayed when Authentication Mode is set to Key authentication.

4. Optional: Upload the required source package before the migration.

   Click Upload and drag the source package to the upload area. Alternatively, you can click Add File to select the source package and click Upload.

   

   The supported source package formats are tar, tar.bz, tar.bz2, tar.gz, tar.xz, tbz, tbz2, tgz, txz, and zip. You can upload multiple source packages at the same time. Each of the source packages must be less than or equal to 1 GB.

5. Click Collect Component to collect component information about the nodes to be migrated. The collection progress is displayed.
6. After the collection is complete, determine whether to enable Trust Current Mirror URL. In the Select Content to Migrate area, select the components to be migrated and the migration target, upload the license certificate, and enter the mirror URL.
   Figure 5 Selecting content to migrate
   
   • License file: Commercial software requires a license file. Click Upload to upload the required license file.
   • Image path: For middleware and databases, enter the image path of the migration target.
   • Optional: Adding or deleting components: Select Operation from the drop-down list and select the components that you want to add or delete.
     • Click Add, enter correct component information, and click OK.
     • Click Delete, check the component information, and click OK.
   

   • If you trust the current mirror URL, SSL certificate verification will be skipped for all software downloads in this migration task. Check that the mirror URL is secure.
   • When selecting the components to be migrated, you can click Save Configuration in the lower left corner to save the current configuration.
7. Click Start Migration.