anthony.wen/cds-ai
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

atvm: default compute migrateops runs to set destination static IP

Browse Source 
Update automation guide defaults so cmc-migrateops-compute-migration includes --set_static_ip_dest by default unless explicitly overridden. Clarify vmware-specific default as vm_platforms selection, and record the behavior change in run learnings for future runs.
This commit is contained in:
anthony.wen
2026-05-07 10:08:23 -04:00
parent 82f285a7b1
commit 28cd8a217f
2 changed files with 13 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
atvm/docs/automation/run-learnings.md
View File

@@ -19,6 +19,13 @@ This file stores run-specific examples only when a run produced a new learning r
- Default to watcher-backed launch using the combined `start-atvm-run.sh` wrapper unless the operator explicitly asks to run without watcher.
- After command execution, report the exact executed `cmc-templates.py` and `run-sorry-cypress.py` command strings in the response.
## Run Learning: 2026-05-07 (Default ATVM compute migrateops runs to set destination static IP)
- Observed requirement:
- ATVM compute migrateops runs should default to enabling destination static IP handling to avoid status-check/parser mismatches and keep destination addressing consistent post-cutover.
- Action for future runs:
- For `cmc-migrateops-compute-migration`, include `--set_static_ip_dest` by default unless the operator explicitly asks not to.
- Keep platform selection (`--vm_platforms ...`) based on the operator request while retaining this static-IP default.
## Run Learning: 2026-05-02 (Do not reuse the previous controller status check for a new ATVM request)
- Observed failure mode:
- A later ATVM run request was blocked because the assistant reused the immediately previous controller status result instead of performing a fresh live running-state check at request time.