alibabacloud-lingjun-node-ops
Alibaba Cloud Lingjun Node Operations (Full Lifecycle)
Scenario Description
Cover the post-provisioning day-to-day operations of Lingjun regular nodes (NodeId) and rack-level hyper-nodes (HyperNodeId). Provisioning/expansion/shrink/release is out of scope here - see the sister skill alibabacloud-lingjun-cluster-scaling. This skill focuses on 9 capability areas / 22 use cases (node-to-group move change-node-group and file delivery send-file are out of scope):
| # | Capability | Mutating CLI | Sync/Async | Reversible |
|---|---|---|---|---|
| F1 | Node Stop | stop-nodes |
Async (TaskId) | Yes (start later via reboot) |
| F2 | Node Reboot | reboot-nodes |
Async (TaskId) | N/A |
| F3 | Node Reimage | reimage-nodes |
Async (TaskId) | No (data loss) |
| F4 | Node Renew | bssopenapi renew-instance |
Sync (OrderId) | No (paid) |
| F5 | Node Spec Change | change-node-types |
Async (TaskId) | Yes (re-issue) |
| F6 | Repair | report-node-status + approve-operation |
Sync | N/A |
| F7 | Run Command | run-command (+ describe-invocations / stop-invocation) |
Async (InvokeId) | N/A |
| F8 | Node Group Update | update-node-group (group default) |
Sync | Yes |
| F9 | Tag & Resource Group | tag-resources / untag-resources / change-resource-group |
Sync | Yes |
Canonical Chinese feature names (MANDATORY in zh sessions) - the authoritative zh rendering strings live in
lib/core/i18n.sh(render.feat.F1..render.feat.F9keys, rendered via_lj_t); the agent must use them verbatim and never free-translate (e.g. F5 must never be rendered with a non-canonical synonym). TheF1-F9codes themselves are internal documentation indices - never show them in any user-facing output (confirmation-table titles, operation names, submission receipts, progress lines, final reports): write the canonical feature name plus the CLI name in parentheses, never the F-code; they may appear only in capability-overview tables that enumerate all features.