huawei-cloud-kunpeng-source-code-migrate

Kunpeng Source Code Migration Assessment

Analyze the migrability of C/C++/ASM/Fortran/Go/Java/Python/Scala source code to Kunpeng (ARM64) platform using Huawei DevKit CLI tool.

Overview

This skill assesses source code migrability to the Kunpeng (ARM64) platform using Huawei DevKit CLI. It connects to a source server via SSH (or installs locally), installs DevKit, scans source code, and generates a migration assessment report. If the user has no remote server, it can automatically provision a Kunpeng ECS instance on Huawei Cloud (Guiyang Region 1) via hcloud CLI.

Architecture: Local detection + remote execution + SFTP transfer. All SSH operations use the unified scripts/ssh_client.py (paramiko + password env var), cross-platform consistent. See the Architecture section below for the full tree.

Applicable scenarios:

• Assess source code portability/migrability to Kunpeng ARM platform
• Scan C/C++/ASM/Fortran/Go/Java/Python/Scala code for migration issues
• Generate a Kunpeng migration assessment report for a software project
• Check source code compatibility with ARM64/Kunpeng architecture
• Provision a Kunpeng server on Huawei Cloud for migration assessment

Report save path (fixed unless user explicitly requests otherwise): Windows → C:\devkit-report\, Linux/macOS → /home/devkit-report/.

Prerequisites

CLI version requirements:

Authentication:

• SSH credentials (existing server, Step 3c): User must set env vars KUNPENG_SERVER_HOST, KUNPENG_SERVER_PORT (default 22), KUNPENG_SERVER_USER (default root), MIGRATE_SSH_PASS in their own terminal. AI must NEVER ask for or echo these values.
• Huawei Cloud AK/SK (provisioning path, Step 3d): User must run hcloud configure set --cli-region=cn-southwest-2 --cli-access-key=<your-ak> --cli-secret-key=<your-sk> in their own terminal. AI must NEVER ask for AK/SK.

IAM permissions (Step 3d only): Required for provisioning a Kunpeng ECS on Huawei Cloud. Minimum set: ECS create/list/delete, VPC create/get/delete, Subnet, SecurityGroup, EIP create/delete, IMS list, IAM projects list. See references/iam-policies.md for the full policy JSON and setup instructions.

OS support: DevKit local install supports openEuler/CentOS/Ubuntu/Kylin/UOS/EulerOS/Debian/SUSE/NeoKylin. Windows and macOS are NOT supported for local install — must use a remote Linux server.

Core Commands

1. Local OS detection:

python <skill_dir>/scripts/detect_os.py

2. SSH connection & remote execution (unified paramiko client):

python <skill_dir>/scripts/ssh_client.py test                              # Test SSH connection
python <skill_dir>/scripts/ssh_client.py exec "uname -a" 30                # Execute remote command
python <skill_dir>/scripts/ssh_client.py put <local> <remote>              # SFTP upload single file
python <skill_dir>/scripts/ssh_client.py put-dir <local_dir> <remote_dir>  # SFTP upload directory
python <skill_dir>/scripts/ssh_client.py get-report                        # Download migration report

3. DevKit installation:

bash <skill_dir>/scripts/install_devkit.sh --yes

4. Source code migration scan (DevKit CLI):

# C/C++ project (with build command):
devkit porting src-mig -i /home/project -s 'c, c++, asm' -b make -c 'make all' -p gcc9.3.0 -o /tmp/devkit-report -r all

# Java/Python project (no build command):
devkit porting src-mig -i /home/project -s 'java, python' -o /tmp/devkit-report -r all

5. Kunpeng ECS auto-provisioning (Step 3d only):

bash <skill_dir>/scripts/provision_kunpeng_server.sh --confirm

6. hcloud CLI install & configure (Step 3d only):

curl -LO "https://cn-north-4-hdn-koocli.obs.cn-north-4.myhuaweicloud.com/cli/latest/huaweicloud-cli-linux-amd64.tar.gz"
tar -xzf huaweicloud-cli-linux-amd64.tar.gz && chmod +x hcloud && sudo mv hcloud /usr/local/bin/
hcloud configure set --cli-region=cn-southwest-2 --cli-access-key=<your-ak> --cli-secret-key=<your-sk>
hcloud version   # Expected: >= 3.2.0

Parameter Confirmation

AI must confirm the following parameters with the user before execution.

SSH connection parameters (env vars, set by user in their own terminal):

DevKit scan parameters (confirm with user before scanning):

⚠️ AI MUST ask the user for the source code path before scanning. Do NOT scan or upload local files without user confirmation.

⛔ Prohibited Operations

If a user requests a prohibited operation, refuse and inform: "Per security constraints, this skill does not allow [specific operation]. Please perform this operation manually if needed."

Architecture

Kunpeng Source Code Migration Assessment
├── DetectLocalOS     (Detect agent OS → determine DevKit install path)
├── PrepareServer     (Determine where to install DevKit and run scan)
│   ├── LocalInstall  (Install DevKit locally — only if OS is supported)
│   ├── RemoteInstall (Install DevKit on remote server via SSH)
│   │   ├── HasServer (Configure SSH via ssh_client.py: paramiko + password env var)
│   │   └── NoServer  (Install hcloud CLI → Provision Kunpeng ECS → Configure SSH)
│   └── NotSupported  (Local OS not supported → must use remote server)
├── ConnectServer     (SSH connect via paramiko + MIGRATE_SSH_PASS env var)
├── InstallDevKit     (Detect OS and install DevKit CLI tool)
└── ScanSourceCode    (Scan source code → generate report → save to fixed local path)
    └── ReportSave    (Windows: C:\devkit-report\ | Linux/macOS: /home/devkit-report/)

⚠️ Task 0 (DetectLocalOS + PrepareServer) MUST be executed first — it determines the entire workflow path.

SSH Connection Strategy

All SSH operations use the unified scripts/ssh_client.py (paramiko + password from env var). No ssh/scp commands, no ControlMaster, no key injection, no Huawei Cloud region dependency. Works identically on Windows, Linux, and macOS.

Environment variables (set by user in their own terminal; AI never sees values):

Setting env vars (cross-platform):

# Linux / macOS (current session):
export KUNPENG_SERVER_HOST='<your-server-ip>'
export KUNPENG_SERVER_PORT='22'
export KUNPENG_SERVER_USER='root'
export MIGRATE_SSH_PASS='<your-password>'

# Windows PowerShell (current session):
$env:KUNPENG_SERVER_HOST='<your-server-ip>'
$env:KUNPENG_SERVER_PORT='22'
$env:KUNPENG_SERVER_USER='root'
$env:MIGRATE_SSH_PASS='<your-password>'

# Windows (persistent, GUI): Settings > Environment Variables > User > New
# (requires IDE/terminal restart)

Credential resolution priority (first match wins):

1. Current process env vars (export / $env:)
2. /tmp/kunpeng_server_env.sh (Linux/macOS) or %TEMP%/kunpeng_server_env.sh (Windows)
3. Windows user-level registry (winreg) — fallback for GUI-set vars
4. Default value

`ssh_client.py` subcommands:

📦 SFTP-First File Transfer (Critical for Windows + MSYS2)

⚠️ On Windows + MSYS2/Git Bash, the shell converts Unix paths in command arguments to Windows paths before Python sees them (e.g., /tmp/foo → C:/Users/.../Temp/2/foo). This cannot be fixed from within Python's sys.argv.

Rule: For file transfer, always use paramiko SFTP API directly from Python, not `ssh_client.py` CLI subcommands.

import os, paramiko
host = os.environ.get('KUNPENG_SERVER_HOST')
port = int(os.environ.get('KUNPENG_SERVER_PORT', '22'))
user = os.environ.get('KUNPENG_SERVER_USER', 'root')
password = os.environ.get('MIGRATE_SSH_PASS')
client = paramiko.SSHClient()
client.set_missing_host_key_policy(paramiko.AutoAddPolicy())
client.connect(host, port=port, username=user, password=password, timeout=30)
sftp = client.open_sftp()
sftp.put(r'C:\local\install_devkit.sh', '/tmp/install_devkit.sh')
sftp.chmod('/tmp/install_devkit.sh', 0o755)
sftp.close()
client.close()

AI agent workflow:

1. File transfer → paramiko SFTP API directly (see above)
2. Command execution → ssh_client.py exec "<cmd>" (short commands only)
3. Script execution → upload via SFTP, then exec "bash /tmp/script.sh"

When ssh_client.py put/get detects a mangled Windows path, it exits with an error directing you to use the paramiko SFTP API directly. See references/scripts-guide.md#sftp-first-file-transfer and references/troubleshooting.md#7-msys2-path-conversion-error-windows-only.

Built-in Scripts

AI MUST use these scripts instead of manually executing step-by-step commands.

📄 Detailed guide → references/scripts-guide.md

Supported Languages

Core Workflows

Task 0: Detect Local OS and Prepare Environment

This is the FIRST task. It detects the agent's local OS and determines the DevKit installation path.

Step 1: Detect local OS:

python <skill_dir>/scripts/detect_os.py

Outputs os_type, os_name, os_version, arch, local_install_supported as key=value pairs. Works on all platforms without external dependencies.

⚠️ AI MUST use `detect_os.py` instead of manually running uname -m, cat /etc/os-release, PowerShell, etc.

DevKit-supported local OS list:

Windows and macOS are NOT supported for local DevKit installation. DevKit must be installed on a remote Linux server.

Step 2: Ask user where to install DevKit

• If local OS IS supported (LOCAL_INSTALL_SUPPORTED=true): Ask "local install" or "remote server install"
• "local install" → Step 3a
• "remote server install" → Step 3b
• If local OS is NOT supported: Ask "existing remote Linux server" or "provision Kunpeng server on Huawei Cloud"
• "existing remote Linux server" → Step 3c
• "provision Kunpeng server" → Step 3d

Step 3a: Local Install

1. Install DevKit: bash <skill_dir>/scripts/install_devkit.sh --yes
2. Ask user for local source code path
3. Run DevKit scan locally (no SSH needed)
4. Skip Task 1 — proceed directly to Task 3 with local paths

📄 Details → references/task-local-devkit.md

Step 3b: Remote Install — Ask about remote server

Ask "existing remote Linux server" or "provision Kunpeng server" → Step 3c or 3d.

Step 3c: User has remote server — Configure SSH

User sets KUNPENG_SERVER_HOST/PORT/USER and MIGRATE_SSH_PASS in their terminal (AI never sees values). Verify:

python <skill_dir>/scripts/ssh_client.py test

⚠️ No region dependency: Remote server can be on any cloud or on-premises. No hcloud CLI needed for SSH.

After verification succeeds, proceed to Task 1.

Step 3d: User has no server — Provision Kunpeng ECS on Huawei Cloud

⛔ CRITICAL: AI MUST use `provision_kunpeng_server.sh` to create ALL cloud resources. NEVER manually call hcloud APIs individually.

1. Check hcloud CLI installation and authentication
2. Confirm provisioning with user (present spec and estimated cost)
3. Execute: bash <skill_dir>/scripts/provision_kunpeng_server.sh --confirm

• Creates VPC → Subnet → Security Group + SSH rule → EIP → ECS
• Generates random root password, saves to /tmp/kunpeng_server_env.sh as MIGRATE_SSH_PASS (chmod 600)

1. Load env: source /tmp/kunpeng_server_env.sh
2. Verify SSH: python <skill_dir>/scripts/ssh_client.py test
3. Proceed to Task 1
4. After scan completes (Task 3): Present Resource Cleanup Reminder

📄 Details → references/task-prepare-server.md

Task 1: Connect to Source Code Server via SSH

Verify connection using python <skill_dir>/scripts/ssh_client.py test. All subsequent operations use ssh_client.py subcommands (see SSH Connection Strategy above).

📄 Details → references/task-connect-server.md

Task 2: Install DevKit CLI Tool

Install DevKit CLI on the target machine using scripts/install_devkit.sh. The script auto-detects OS/architecture, installs dependencies, downloads the correct package, and verifies installation.

⚠️ AI MUST use `scripts/install_devkit.sh` instead of manually running step-by-step commands.

📄 Details → references/task-install-devkit.md

Task 3: Scan Source Code and Generate Migration Report

⚠️ CRITICAL RULES:

1. MUST ask user for the source code path before scanning. Do NOT scan without user confirmation.
2. MUST NOT scan local source code without permission.
3. MUST NOT upload local files to remote server without permission.
4. CAN list available source code directories on remote server to help user choose.

Report save path (local download):

The skill MUST create the directory if it does not exist. Report files (HTML, JSON, CSV) MUST be saved directly under <save_path>/ (no project_name subdirectory). This path is fixed unless user explicitly requests a different location.

Downloading the report:

# Download with defaults (remote=/tmp/devkit-report, local=C:\devkit-report on Windows):
python <skill_dir>/scripts/ssh_client.py get-report

# Or specify custom paths:
python <skill_dir>/scripts/ssh_client.py get-report /tmp/devkit-report /home/devkit-report

⚠️ AI MUST use `get-report` (or paramiko SFTP API) to download the report. Do NOT use exec with base64/cat to download files.

📄 Details → references/task-scan-source-code.md

DevKit CLI Command Reference

The primary tool is Kunpeng DevKit CLI (devkit command).

Source migration command:

devkit porting src-mig -i <source_path> -o <output_path> -s '<language_list>' [options]

Required parameters:

Optional parameters:

Language values (`-s`): c, c++, asm, fortran, go, java, python, scala (lowercase, comma-separated)

Compiler versions (`-p`): gcc4.8.5, gcc7.3.0, gcc9.3.0, gcc10.3.0, gcc12.3.0, bisheng compiler3.0.0, bisheng compiler4.0.0, gcc for openeuler3.0.3, etc.

Scan examples:

# C/C++ project with make build:
devkit porting src-mig -i /home/project -s 'c, c++, asm' -b make -c 'make all' -p gcc9.3.0 -o /tmp/report -r all

# Java/Python project (interpreted, no build command):
devkit porting src-mig -i /home/project -s 'java, python' -o /tmp/report -r all

⚠️ The `devkit` binary must be run from its installation directory (e.g., cd /usr/local/devkit && ./devkit), or the directory must be in PATH. The output directory (-o) must already exist.

📄 Full CLI reference → references/devkit-cli-reference.md

References

Resource Cleanup Reminder

⚠️ After the scan completes and the report is presented, AI MUST remind the user to clean up provisioned resources (applies to Step 3d provisioning path only). Present as TEXT ONLY — never execute delete commands.

### 🧹 Resource Cleanup Reminder

The following resources were created during this assessment and incur ongoing charges:

| Resource Type | Resource ID | Details |
|---------------|-------------|---------|
| ECS Instance  | <id>        | <IP>, <flavor> |
| VPC           | <id>        | <name> |
| Subnet        | <id>        | <name> |
| EIP           | <id>        | <IP> |
| Security Group| <id>        | <name> |

To delete these resources, execute the following commands manually:

  [delete commands here]

⚠️ WARNING: Deletion is IRREVERSIBLE. Verify resource IDs before executing.
⚠️ AI will NOT execute these commands. Please run them manually.

For Step 3c (existing server) and Step 3a (local install): No cleanup reminder needed — user provided their own server or installed DevKit locally.