Documentation
Rate This Document
Findability
Accuracy
Completeness
Readability
SubmitClose

Workload Assessment

Parameter Description

Table 1 Workload assessment items

Workload

Description

Promote and expand the ecosystem

This workload goes through ecosystem development, adaptation process tracking, and migration assistance.

Conduct surveys on applications

Investigate technology details and metrics of applications and service scenarios.

Design the migration solution

Analyze migration requirements and make a migration plan. Analyze the technology stack of the target software, assess the feasibility and workload of component adaptation, and make a work plan.

Launch for commercial use

After compiling and migrating application software, launch the version for commercial use. This workload is limited to version launch.

Prepare test resources

Prepare resources such as physical servers, remote labs, and cloud servers for adaptation and testing, including installing and powering on physical servers and applying for remote access accounts.

Prepare the software environment

Install the OS, compiler, JDK, and other tool software that can be directly used without recompilation.

Prepare the source code of open source dependencies

Obtain the open-source dependency source code and SO library files, either by git clone or source code download.

Compile and package open source dependencies

Compile and package the open-source dependency source code in the compilation environment.

Connect to Huawei or third-party products

Connect to Huawei or third-party products, including API interconnection, troubleshooting, and testing.

Modify and compile self-developed code
  • Modify and debug part of C, C++, and Fortran compiled code in self-developed software. The workload is subject to the amount of the modified and debugged C, C++, and Fortran code.
  • Debug interpreted code such as Java/Python code in self-developed software. Interpreted code does not need to be modified or compiled. It can be ported after debugging.

ISV's test

The ISV performs tests based on the software design specifications and test cases, including unit tests, API tests, system function tests, and other baseline tests. The workload is subject to the number of test cases. Enter the actual number of test cases.

Joint test

The ISV and Huawei perform joint tests, including system function tests, service integration tests, performance tests, and tuning tests. The workload is subject to the number of test cases. Enter the actual number of test cases.

Calculation Formula

You can modify the parameter values of workload assessment in the /opt/DevKit/devkitplugins/porting/config/xc_model/workload_model.json file. /opt is the tool installation directory. Replace it with the actual directory.

Table 2 Parameters in the workload_model.json file

Parameter

Description

xx_keyword

Name of the work item.

max

Maximum value of the work item.

min

Minimum value of the work item.

standard

Weight of the work item. The actual workload is equal to the number of tasks in the work item multiplied by the value of standard.

Take ISV's test as an example. If the number of test cases is 500 and the default weight is 0.1, the workload is 50 person-days (500 x 0.1).

default

Default value of the work item.

The formula for calculating the workload is as follows:

Total workload = "Promote and expand the ecosystem" + "Conduct surveys on applications" + "Design the porting solution" + "Launch for commercial use"
         + Number of compiled code lines x Weight of compiled languages (0.04 by default)
         + Number of interpreted language modules x Weight of interpreted languages (four times the number of Java applications, excluding those Compatible ones)
         + Number of the ISV's test cases x Weight of the ISV's test (0.1 by default)
         + Number of joint test cases x Weight of the joint test (0.1 by default)
         + Deployment scale x Weight of "Prepare test resources" (0.5 by default)
         + Quantity of tool software x Weight of "Prepare the software environment" (0.5 by default. The tool software here indicates the OS, compiler, JDK, and other tool software that do not need to be recompiled.)
         + Number of open source components x (Weight of "Prepare the source code of open source dependencies" + weight of "Compile and package open source dependencies")
         + Quantity of middleware x Weight of "Connect to Huawei or third-party products" (15 by default)

The default workload is 2 person-days for "Promote and expand the ecosystem", "Conduct surveys on applications", "Design the porting solution", and "Launch for commercial use." If all migration items are Compatible, the workload is 0 person-days.

If the workload_model.json file is mis-deleted, the default model file in the /opt/DevKit/devkitplugins/porting/config/xc_model/xc_model_bak backup path is read. If you need to modify the default file, copy the default file to the xc_model directory:

cd /opt/DevKit/devkitplugins/porting/config/xc_model
cp xc_model_bak/workload_model_bak.json workload_model.json
chown -R devkit:devkit workload_model.json
chmod 644 workload_model.json