Creating a System Migration Project

This feature analyzes installed software such as software packages, middleware, and databases in an application system, and provides a migration assessment report and migration guidance.

Prerequisites

You have logged in to the Kunpeng DevKit.
You have added the system that you want to migrate and you have imported component information to the system.

Procedure

Click System Migration in the navigation tree on the left and then click

to go to the Migration Project Creation tab page.

Figure 1 Creating a migration project

**Table 1** Parameter description
Parameter	Description
Migration Project Name	A project name is automatically generated by default, which can be modified as required.
System to Be Migrated	Select the system that you have added. Ensure that you have imported component information to the system.

Click Verify and Proceed. In Migration Path, select the node information, migration target, and target version.
On the server where the tool is installed, maintenance personnel can modify the /opt/DevKit/devkitplugins/porting/config/migration_route.json file to update the migration paths supported by the tool. After the modification is complete, restart the DevKit service. /opt is the tool installation directory. Replace it with the actual directory.
```
systemctl restart gunicorn_plugin.service
```

Click Next. The migration assessment progress is displayed. When the progress is complete, the Migration Assessment page is displayed.

By default the Migration Difficulty Assessment tab page is displayed, as shown in Figure 2. Table 2 describes the parameters.

Figure 2 Migration Difficulty Assessment

**Table 2** Parameter description
Parameter	Description
Migration Difficulty Assessment	Migration difficulty score and workload.
For the detailed assessment scores, see Migration Difficulty Scores.
Dimension/Type/Metric	Scores of each dimension, type, or metric.
Maximum Score	Assessment criterion of each dimension, type, or metric, that is, the maximum possible score.
Actual Score	Actual score of each dimension, type, and metric.
For workload assessment details, see Workload Assessment.
Workload Item	Details about each assessed migration item.
Workload (Person-Days)	Estimates the manpower required for each migration item.

Assessment Settings
You can click Assessment Settings to modify migration assessment parameters. After the modification is complete, click OK to make the modification take effect immediately. The Lines of compiled language setting belongs to the type of Modify and compile self-developed code.

Click the Migration Compatibility Assessment tab to view the migration compatibility assessment information. Table 3 describes the parameters.

Figure 3 Migration Compatibility Evaluation

**Table 3** Parameter description
Parameter	Description
Compatibility Statistics	Number of compatible, adaptable for compatibility, incompatible, and to-be-confirmed items.
Migration Statistics	Numbers of easy, medium, difficult, and unsupported items.
System Components
No.	Node SN.
Node Name	Name of the migrated node.
IP Address	IP address of the migrated node.
Components	Total number of components on the migrated node.
Easy	Number of the components that can be migrated with ease. Little effort is needed for the migration.
Medium	Number of the components that are relatively difficult to be migrated. A small amount of modification based on the guidance is required for the migration.
Difficult	Number of the components that are difficult to be migrated. A large amount of code must be reconstructed for the migration.
Not Supported	Number of the components that are not supported for the migration. No guidance is provided by the tool.
Compatible	Number of the components on the node, such as databases, middleware, and Java applications, that are compatible with the target environment.
Adaptable for Compatibility	Number of database, middleware, and Java application components that are not compatible with the target environment yet, but can be compatible through tool assistance.
To Be Confirmed	Number of the components whose compatibility needs to be confirmed. You can contact DevKit technical support for the confirmation or confirm the compatibility based on your own experience. NOTE: Run the software on the Kunpeng platform and check whether the running is normal. If yes, the software is compatible with Kunpeng. If no, modify the software code based on the located native functions.
Incompatible	Number of the components on the node that are incompatible with the target environment.
Operation	You can click View to view the details.

Click the Task Information tab to view the project name, project update time, information system, analysis status, and migration path.
Figure 4 Task information

Click Next to go to the Migration Guidance page.

By default the Migration Guidance Report tab page is displayed, as shown in Figure 5. Table 4 describes the parameters.

Figure 5 Migration guidance report

You can click next to the Select Node drop-down list to filter the nodes you want to check and view the guidance details for them.
You can click a guidance rule name to view the rule details on the right.

Click

to view guidance details.

For the Component object type, click View Guidance, and the suggestion details and guidance are displayed on the right. For the File object type, click View Guidance, and the Guidance Summary is displayed.

**Table 4** Guidance details
Parameter	Description
Component Adaptation Statistics	Total number of components to be adapted, and numbers of replaceable, to-be-modified, and to-be-rebuilt components. Replaceable: Replace them with alternatives. To Be Modified: Detailed modification points are clarified or an adaptation solution without details is provided. To Be Rebuilt: Rebuild them because they are incompatible and no adaptation solution is available.
File Adaptation Statistics	Number of to-be-modified configuration files and the estimated number of lines of adapted items.
Guidance Rule	Name of the guidance rule.
Rule ID	ID of the guidance rule. By default, the guidance rule ID is not displayed.
Object Type	Type of a guidance rule, which can be Component or File.
Software Type	Software type of the guidance rule, which can be Java application, Java runtime, Database, Middleware, Hardware, or OS.
Label	Label of the guidance rule.
Priority	Priority of the migration guidance, which can be High, Medium, or Low.
Story Point	A story point is a metric used to estimate the workload of implementing a given user task, which is an abstract measure of effort required to implement it. A larger value indicates a higher complexity or difficulty. A larger value indicates a higher complexity or difficulty. The details are as follows: 0: The migration priority is very low or modifications are not required. 1: Only a few libraries need to be replaced or simple modifications on interfaces are required. 3: Complex modifications are required and available guidance and solutions are provided. 5: Redesign or a large amount of code reconstruction is required. 7: Redevelopment and reconstruction of the component or subsystem is required. 13: No available guidance and solutions are provided currently.
Status	Status of the migration guidance, which can be Executed, Not executed, or Masked.
Remarks	Supplementary description of the migration guidance.
Status Updated	Time when the guidance rule status is updated.
Operation	You can edit the guidance rule status and remarks, and view the migration guidance.
Component Name	Component name.
File Name	File name.
Source Path	Source path of the component or file.
Guidance Suggestion	Detailed guidance for the migration.
Rows to Modify	Number of rows to be modified in a file. This parameter is available when Object Type is File.
Analysis Result	The options are Replaceable, To Be Modified, or To Be Rebuilt. This parameter is displayed when Object Type is Component.

If a guidance rule has been modified according to the suggestion, change its Status to Executed. For a guidance rule that is unimportant or has no impact, change its Status to Masked.
- Choose Operation > Edit to modify the Status of a single guidance rule. Click OK to save the modification.
- You can select multiple guidance rules and click Batch Edit to edit them at the same time. Click OK to save the modification.

Click Guidance Summary. The result page for the file to be adapted is displayed.

Figure 6 Guidance summary

**Table 5** Parameters of **Guidance Summary**
Parameter	Description
File List	Name of the file to be analyzed. You can select a node from the drop-down list to view the target file.
To-Be-Adapted File	Details about the file to be adapted. You can perform modification based on the locations and suggestions.

You can click the arrow keys in the upper right corner of the To-Be-Adapted File module to go up and down.

Click the Task Information tab to view the project name, project update time, information system, project status, and migration path.

Related Tasks

To stop a system migration project, click next to the project, or click next to the information system and then click Stop Project in the Operation column.
To delete a system migration project, click next to the project, or click next to the information system and then click Delete in the Operation column.

If you click next to the information system, all migration projects for the information system will be deleted. If you click next to System Migration, all migration projects will be deleted. Deleted data cannot be recovered. Exercise caution when performing this operation.
To change the name of a system migration project, click next to the system project, rename the project, and click OK.

Parent topic: System Migration Project Management