Huawei Cloud ECS Lifecycle Management

Full lifecycle management for Huawei Cloud Elastic Cloud Server (ECS) — from provisioning to decommissioning, including power-state orchestration and instance queries.

Overview

This Skill manages the complete lifecycle of ECS (Elastic Cloud Server) instances on Huawei Cloud using the KooCLI ECS service (with the huaweicloudsdkecs Python SDK as fallback):

Scope note: All mutating operations (create / delete / start / stop / reboot / rename) are executed only after explicit user confirmation. Query operations are safe to run anytime.

Prerequisites

1. KooCLI (hcloud) installed and authenticated — see references/cli-installation-guide.md
2. Region — pass --cli-region=cn-north-4 (use the account's region; e.g. cn-north-4), or the active CLI profile default is used
3. IAM permissions — the authenticated account needs the ECS permissions listed in references/iam-policies.md (least privilege)
4. Python 3.8+ with huaweicloudsdkecs (only needed for the SDK fallback path)

Quality Reporting Environment Variables

Workflow

1. Classify the request — knowledge question (answer inline from the Overview/FAQ below and official docs) or an ECS operation.
2. Resolve the target server(s) — for instance-specific operations, get server_id from the user, or list instances first (ListServersDetails) if the ID is unknown.
3. Query operations — build the command with the requested filters and execute directly.
4. Mutating operations — present the exact command and parameters to the user, wait for explicit confirmation, then execute. If the CLI fails (e.g. SDK/permission error), fall back to the huaweicloudsdkecs SDK equivalent.
5. Report — return the operation result (job ID, affected instance IDs, or detailed instance info) and, for state-change operations, suggest verifying with ListServersDetails.

Core Commands

All commands below use --cli-region=cn-north-4 as the example region; use the authenticated account's region instead (or rely on the CLI profile default). Required parameters are always shown; the most common optional parameters are included. Parameter names were verified against the KooCLI --help output of each ECS operation. Example names/IDs are placeholders to be replaced with real values from the user's environment.

List ECS instances

hcloud ECS ListServersDetails --cli-region=cn-north-4 --limit=25 --name=my-ecs --status=ACTIVE

Show ECS instance detail

hcloud ECS ShowServer --cli-region=cn-north-4 --server_id=6a2f0b1c-8d4e-4f3a-9b7c-1d2e3f4a5b6c

Create ECS instance(s)

Confirmation required before execution. Creating instances incurs billing.

hcloud ECS CreateServers --cli-region=cn-north-4 --server.name=my-ecs --server.flavorRef=s6.large.2 \
  --server.imageRef=9c2f377e-7f3a-4f4e-9c1a-2b3c4d5e6f7a --server.vpcid=81a7f347-8f0e-4b2a-9c4d-5e6f7a8b9c0d \
  --server.nics.1.subnet_id=04e00f59-1a2b-3c4d-5e6f-7a8b9c0d1e2f --server.root_volume.volumetype=SSD \
  --server.security_groups.1.id=41a937e1-9b8c-7d6e-5f4a-3b2c1d0e9f8a --server.availability_zone=cn-north-4a \
  --server.count=1 --server.adminPass=Huawei@123

Note: Both parameters above are marked Yes (in practice). They are optional at the API schema level, but in practice omitting them fails ECS creation in most VPC configurations: --server.nics.[N].subnet_id is required unless the VPC default subnet is used, and --server.security_groups.[N].id is commonly required by the API's VPC configuration. For pay-per-use only: CreateServers with --server.extendparam.chargingMode=0; use CreatePostPaidServers for a simpler pay-per-use flow if preferred.

Delete ECS instance(s)

Confirmation required before execution. Data on disks may be lost when --delete_volume=true.

hcloud ECS DeleteServers --cli-region=cn-north-4 --servers.1.id=6a2f0b1c-8d4e-4f3a-9b7c-1d2e3f4a5b6c --delete_publicip=false --delete_volume=false

Start ECS instance(s)

Confirmation required before execution.

hcloud ECS BatchStartServers --cli-region=cn-north-4 --os-start.servers.1.id=6a2f0b1c-8d4e-4f3a-9b7c-1d2e3f4a5b6c

Stop ECS instance(s)

Confirmation required before execution. HARD stop may lose unsaved data.

hcloud ECS BatchStopServers --cli-region=cn-north-4 --os-stop.servers.1.id=6a2f0b1c-8d4e-4f3a-9b7c-1d2e3f4a5b6c --os-stop.type=SOFT

Reboot ECS instance(s)

Confirmation required before execution. HARD reboot may lose unsaved data.

hcloud ECS BatchRebootServers --cli-region=cn-north-4 --reboot.servers.1.id=6a2f0b1c-8d4e-4f3a-9b7c-1d2e3f4a5b6c --reboot.type=SOFT

Rename ECS instance(s)

Confirmation required before execution.

hcloud ECS BatchUpdateServersName --cli-region=cn-north-4 --name=my-ecs-renamed --servers.1.id=6a2f0b1c-8d4e-4f3a-9b7c-1d2e3f4a5b6c

Parameter Confirmation

--project_id is auto-resolved by KooCLI from the authenticated credentials; --cli-region is the only parameter the agent must always supply explicitly.

Basic ECS FAQ (Knowledge Q&A)

• What is ECS? Elastic Cloud Server — Huawei Cloud's IaaS compute service. Instances can be provisioned in minutes with flexible flavors, images, disks, and networks.
• Flavors — defined by vCPUs/memory (e.g. s6.large.2 = 2 vCPU / 4 GB). Query available flavors via hcloud ECS ListFlavors --cli-region=cn-north-4.
• Billing — pay-per-use (按需) or yearly/monthly (包年/包月); spot instances (竞价) available.
• Login — keypair (recommended) or password. For password login the initial password is set at creation (adminPass / user_data).
• Status values — ACTIVE (running), SHUTOFF (stopped), BUILD (creating), REBOOT, ERROR, MIGRATING, RESIZE, SHELVED, DELETED.

Reference Documents

• references/iam-policies.md — Least-privilege IAM policies for ECS lifecycle operations
• references/cli-installation-guide.md — KooCLI installation and authentication
• references/verification-method.md — How to verify each operation
• references/dataflow-diagram.md — Mermaid data flow diagram
• references/acceptance-criteria.md — Acceptance criteria for this skill

KooCLI Command Format Standard

Every KooCLI command is built as: hcloud + service name (ECS) + operation name (PascalCase) + region parameter --cli-region=<region> + parameter key-value pairs (--key=value). Only the executable examples in Core Commands are meant to be run directly.

Edge Cases

Quality Reporting

This Skill integrates scripts/skill_quality_sdk.py for execution quality reporting. Every run reports trace_id, status (success/biz_fail/sys_fail/cancel), error code, cost, and masked input/output.

Integration

• Python entry point: wrap execution with quality_context:

  from skill_quality_sdk import quality_context
  with quality_context(skill_name="huawei-cloud-ecs-lifecycle") as q:
      q.input = {"operation": "ListServersDetails", "region": "cn-north-4"}
      result = run_ecs_operation()
      q.output = result
  

• CLI self-check: python3 scripts/skill_quality_sdk.py (sends one test report).

Error Code Convention

Non-blocking, fail-silent. Disable with SKILL_QUALITY_DISABLE=1 for local testing.