Documentation
Rate This Document
Findability
Accuracy
Completeness
Readability
SubmitClose

Batch Importing Source Components

System Migration allows batch importing source components and manually adding component information. If you perform a batch import, you can run the script to obtain the component information on the source node.

Prerequisites

  • You have obtained the node information collection script (devkit_disk_scan.sh).

    On the New Project page, click Batch Import Source Components and obtain the node information collection script as prompted.

  • During a scan, the available space on the partition where the output directory resides is checked. To prevent the drive from running out of space, the available space must be at least 2 GB or 5% of the total space, whichever is smaller.

Procedure

  1. Use an SSH tool to remotely log in to the source node (x86) as the root user and upload the obtained node information collection script to the user-defined directory.
  2. Go to the script directory and run the following command to obtain the source node component information:
    1
    bash devkit_disk_scan.sh

    If the command output contains the following information, the collection is complete. Obtain the compressed package devkit-component-xx.xx.xx.xx-Timestamp.tar.gz.

    [2025-10-31 16:31:13] [INFO] Generated a package: /home/devkit-component-package/result/devkit-component-xx.xx.xx.xx-20251031162830.tar.gz (sha256=692af1c46b7528cecc56ed8dcd54629b0a0224d6127c2b1e846b33a2e5c9772b size=487856342)
[2025-10-31 16:31:13] [INFO] Packaging completed.
    Table 1 Parameter description

    Parameter

    Description

    -h

    Displays help information.

    -R <path>

    Scan directory. It is an absolute path and defaults to the root directory (/).

    Example: -R /home

    NOTE:

    By default the root directory is scanned. A scan may take a long time. Please wait.

    -O <out_path>

    Directory for storing scan results, which defaults to /home. Scan reports are automatically stored in <out_path>/devkit-component-package.

    Example: -O /data

    -p <num>

    Maximum number of processes to be scanned, which defaults to 1.

    Example: -p 8

    -g <DEBUG|INFO>

    Log level, which defaults to INFO.

    • DEBUG
    • INFO

    -N

    Static scan (not to run the --version command to identify the version). This option is enabled by default.

    -z

    Number of concurrent processes for packaging files, which defaults to 1.

    Example: -z 2

    -b

    Background script, which can be replaced with the nohup command.

    -L <file>

    Background redirection log file, which defaults to <out_path>/devkit-component-package/devkit-component-<IP_address>/scan.log.

    -P <file>

    Writes the background process ID to the file. It is recommended that this option be used together with the -b option. The file defaults to <out_path>/devkit-component-package/devkit-component-<IP_address>/devkit-scan.pid.

    -S

    Indicates that you can query the running status (depending on the PID file) in the background.

    • If you use the -P option for the scan, specify -P to obtain the PID file.
    • If you use the -O option but not -P for the scan, specify -O to obtain the PID file.

    -K

    Stops running in the background (depending on the PID file).

    • If you use the -P option for the scan, specify -P to obtain the PID file.
    • If you use the -O option but not -P for the scan, specify -O to obtain the PID file.