Documentation
Rate This Document
Findability
Accuracy
Completeness
Readability
SubmitClose

Creating a Migration Project

Manually add system components in a container migration (for middleware and Java applications) or a non-container migration (for databases, middleware, and Java applications).

Middleware containers support Redis, Nginx, and Nacos.

Prerequisites

You have logged in to the Kunpeng DevKit.

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.
  • You can manually add a local node (that is, the current DevKit node) as a migration project node.

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 New 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, periods (.), hyphens (-), and underscores (_).
    • 1 to 64 characters.
  3. Under Component Table, configure the components that you want to migrate.
    • 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.
    • If the information of some selected components is incomplete, the components are marked with red dots. You need to complete the information before starting the migration.
    • The target nodes support Kylin V10 SP3 (Arm) and UOS V20 (Arm).
    • Method 1: Batch importing source components
      1. Click Batch Import Source Components next to Component Table. In the dialog box that is displayed, import the source components to be parsed and select the target node.
        Figure 2 Batch Import Source Components
      2. Import a compressed package of source components or a Docker Compose file.
        • Compressed package: Use a script to collect information about the database, middleware, application packages, and configuration files on the source node. After the collection is complete, the collected data is compressed into a package. For details, see Batch Importing Source Components.
        • Docker Compose file: You can parse a Docker Compose file to obtain the container components in the file.

          Docker Compose is a tool for defining and running multi-container applications. It is the key to unlocking a streamlined and efficient development and deployment experience. Compose simplifies the control of your entire application stack, making it easy to manage services, networks, and volumes in a single, comprehensible YAML configuration file.

      3. Select the target node and click OK. You can search for a node by its IP address. If no node is found, click Add Node to add one. A maximum of 20 nodes can be added. For details, see Managing Agent.
      4. After importing components, click Edit in the Operation column to complete the configuration.
        Table 1 Import the component information

        Parameter

        Description

        Container Migration

        Indicates whether to migrate a container. This parameter cannot be modified.

        Component Belonging

        The options are Database, Middleware, and Application.

        Source Node

        Enter the IP address of the node where the source component is located.

        Target Node

        You can search for a target node by its IP address. If no target node is found, click Add Node to add one. A maximum of 20 nodes can be added. For details, see Managing Agent.

        Source component

        Source Component Name

        Name of the source component to be migrated.

        Version

        Source component version. This parameter is available only to databases and middleware.

        Origin of Source Component

        It is Batch Import Source Components by default and cannot be changed.

        Source Component Path

        Path to the source component. It cannot be modified.

        Target component

        Target Component Name

        Name of the target component.

        Origin of Target Component

        Indicates where the target component comes. This parameter is available only to databases and middleware.

        • 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 target node and start an automatic installation.
          1. Access the Kunpeng mirror site to obtain the component installation package.
          2. Log in to the tool through SSH and upload the installation package to a user-defined directory on the node server.
          3. Specify the installation package path as the target component path.
        • Upload Target Component Package: Click download the component package in the lower part of the dialog box to obtain the target component package.

        URL

        Enter the target URL.

        NOTE:

        This parameter is displayed when Origin of Target Component is set to Download from URL.

        Target Component Path

        Enter the path to the target component on the target node.

        NOTE:

        This parameter is displayed when Origin of Target Component is set to Obtain from node server.

        Upload Target Component Package

        Click Upload to upload the required target component package in .zip, .tar, or .tar.gz format.

        NOTE:

        This parameter is displayed when Origin of Target Component is set to Upload 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

        Click Upload to upload the required commercial certificate.
        Table 2 Compose component information

        Parameter

        Description

        Container Migration

        Indicates whether to migrate a container. This parameter cannot be modified.

        Component Belonging

        The options are Middleware and Application.

        Source Node

        Enter the IP address of the node where the source component is located.

        Target Node

        Select a target node. You can search for a node by its IP address. If no node is found, click Add Node to add one. A maximum of 20 nodes can be added. For details, see Managing Agent.

        Source component

        Source Component Name

        Name of the migrated source component.

        Origin of Source Component

        Imported Docker Compose file.

        Complete the following advanced settings for a more smooth migration.

        Dockerfile

        Click Upload to upload the required Dockerfile.

        Origin of Image
        • Obtain from node server: Obtain the image file from the specified path on the target node, scan and analyze it, and generate a migration guide report.
        • Upload image: Upload the image file for scanning and analysis and generate a migration guide report. If the image file is greater than the upper limit (2048 MB by default), select Obtain from node server.

        Image
        • If Origin of Image is set to Obtain from node server, enter the path to the image file on the target node.
        • If Origin of Image is set to Upload image, click Upload to upload the required image file.

        env_file

        Click Upload to upload the required env_file.

        Origin of Mounted Volume
        • Obtain from node server: Obtain the mounted volume file from the specified path on the target node, scan and analyze the file, and generate a migration guide report.
        • Upload mounted volume: Upload the mounted volume file for scanning and analysis and generate a migration guide report. If the file is greater than the upper limit (2048 MB by default), select Obtain from node server.

        Mounted Volume
        • If Origin of Mounted Volume is set to Obtain from node server, enter the path to the mounted volume file on the target node.
        • If Origin of Mounted Volume is set to Upload mounted volume, click Upload to upload the required mounted volume file.

        Origin of Container Layer
        • Obtain from node server: Obtain the container layer file from the specified path on the target node, scan and analyze the file, and generate a migration guide report.
        • Upload container layer: Upload the container layer file for scanning and analysis and generate a migration guide report. If the file is greater than the upper limit (2048 MB by default), select Obtain from node server.

        Container Layer
        • If Origin of Container Layer is set to Obtain from node server, enter the path to the container layer file on the target node.
        • If Origin of Container Layer is set to Upload container layer, click Upload to upload the required container layer file.

        Origin of Redis Data File
        • Obtain from node server: Obtain the Redis data file from the specified path on the target node, scan and analyze the file, and generate a migration guide report.
        • Upload Redis data file: Upload the Redis data file for scanning and analysis and generate a migration guide report. If the file is greater than the upper limit (2048 MB by default), select Obtain from node server.

        Redis Data File
        • If Origin of Redis Data File is set to Obtain from node server, enter the path to the Redis data file on the target node.
        • If Origin of Redis Data File is set to Upload Redis Data File, click Upload to upload the required Redis data file.

        Target component

        Target Component Name

        Target component name.

        Origin of Target Component

        Imported Docker Compose file.
    • Method 2: Adding container or non-container component information manually
      1. Click Add Component Information.
      2. Enter component information. Table 3 and Table 4 describe the parameters.
        Figure 3 Adding components
        Table 3 Non-containerized components

        Parameter

        Description

        Container Migration

        Indicates whether to migrate a container.

        Component Belonging

        The options are Database, Middleware, and Application.

        Source Node

        Enter the IP address of the node where the source component is located.

        Target Node

        Select a target node. You can search for a node by its IP address. If no node is found, click Add Node to add one. A maximum of 20 nodes can be added. For details, see Managing Agent.

        Source component

        Source Component Name

        Name of the source component to be migrated.

        Version

        Source component version. This parameter is available only to databases and middleware.

        Origin of Source Component

        Indicates where the source component comes. This parameter is available only to middleware and applications.

        NOTE:

        For details about how to package source components (except the RabbitMQ middleware), see Migration Source Component Preparation Guide.

        • Obtain from node server: Obtain the source component package from the specified path on the target 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.

        Source Component Path

        Path to the source component on the target node.

        NOTE:

        This parameter is displayed when Origin of Source Component is set to Obtain from node server.

        Upload Source Package

        Click Upload to upload the required source component package in .zip, .tar, or .tar.gz format.

        NOTE:

        This parameter is displayed when Origin of Source Component is set to Upload source component package.

        Target component

        Target Component Name

        Name of the target component.

        Origin of Target Component

        Indicates where the target component comes. This parameter is available only to databases and middleware.

        • 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 target node and start an automatic installation.
          1. Access the Kunpeng mirror site to obtain the component installation package.
          2. Log in to the tool through SSH and upload the installation package to a user-defined directory on the node server.
          3. Specify the installation package path as the target component path.
        • Upload Target Component Package: Click download the component package in the lower part of the dialog box to obtain the target component package.

        URL

        Enter the target URL.

        NOTE:

        This parameter is displayed when Origin of Target Component is set to Download from URL.

        Target Component Path

        Enter the path to the target component on the target node.

        NOTE:

        This parameter is displayed when Origin of Target Component is set to Obtain from node server.

        Upload Target Component Package

        Click Upload to upload the required target component package in .zip, .tar, or .tar.gz format.

        NOTE:

        This parameter is displayed when Origin of Target Component is set to Upload 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

        Click Upload to upload the required commercial certificate.
        Table 4 Containerized components

        Parameter

        Description

        Container Migration

        Indicates whether to migrate a container.

        Component Belonging

        The options are Middleware and Application.

        Source Node

        Enter the IP address of the node where the source component is located.

        Target Node

        Select a target node. You can search for a node by its IP address. If no node is found, click Add Node to add one. A maximum of 20 nodes can be added. For details, see Managing Agent.

        Source component

        Source Component Name

        Name of the source component to be migrated.

        Version

        Source component version. This parameter is available only to middleware.

        Origin of Source Component

        The options are:

        • Dockerfile (selected by default for middleware)
        • Image

        Dockerfile

        Click Upload to upload the required Dockerfile.

        Origin of Image
        • Obtain from node server: Obtain the image file from the specified path on the target node, scan and analyze it, and generate a migration guide report.
        • Upload image: Upload the image file for scanning and analysis and generate a migration guide report. If the image file is greater than the upper limit (2048 MB by default), select Obtain from node server.
        NOTE:

        This parameter is available when Origin of Source Component is set to Image.

        Image

        Click Upload to upload the required image file.

        NOTE:

        This parameter is displayed when Origin of Image is set to Upload image.

        Target component

        Target Component Name

        Target component name.

        Origin of Target Component

        Indicates where the target component comes.
      3. Click OK.
  4. 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.

  5. Check whether the source code is available.

    If the source code of the application package is available, continue to migrate the database, middleware, and applications, and use the Source Code Porting function to migrate SQL statements and configurations. If it is unavailable, select No to migrate SQL statements and configurations.

    If you choose to port without source code, the uploaded application packages are classified, and non-open-source JAR packages need to be decompiled and analyzed. You can specify the JAR packages and group IDs to be filtered out by following instructions in Ignoring Files.

    Figure 4 Porting without source code
    Table 5 SQL migration parameters

    Parameter

    Description

    Migration Source Database

    Select the source database to improve the accuracy of migrating source code SQL statements.

    NOTE:

    During migration from MySQL to Vastbase, if Vastbase-transform.jar is not deployed in the current environment, you need to configure the related download information. SQL statement compatibility assessment and conversion will not be performed.

    Migration Target Database

    Select the target database to improve the accuracy of migrating source code SQL statements.

    Origin of Tool Package

    Where the tool package comes.

    • Download from URL: Vastbase-transform.jar is automatically downloaded from the Kunpeng mirror site to the DevKit node.
    • Upload tool package: Copy the tool package download link in the information below and obtain Vastbase-transform.jar.

    Upload Tool Package

    Click Upload to upload the downloaded Vastbase-transform.jar.

    NOTE:

    This parameter is displayed when Origin of Tool Package is set to Upload tool package.

    DDL

    You are advised to configure a DDL for each of the SQL source packages to be scanned. A DDL file records complete information about database tables and fields. DDL statements can improve the accuracy of SQL statement parsing. For details about how to obtain a DDL file, see Exporting a DDL File.

    Migration Target Middleware Type
    • N/A
    • BES migration strategy: The uploaded source package contains the built-in Tomcat configuration files and you need to migrate to the built-in BES files.
    • TongTech migration strategy: The uploaded source package contains the built-in Tomcat configuration files and you need to migrate to the built-in TongTech files.
  6. Click Start.
Parent topic: System Migration