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

Show full template test flow in ATVM status

Browse Source
This commit is contained in:
anthony.wen
2026-03-27 10:19:02 -04:00
parent 2699651f8f
commit 53f9e68fcd
4 changed files with 84 additions and 32 deletions
Download Patch File Download Diff File Expand all files Collapse all files

35
atvm/docs/automation/status-template.md
View File

@@ -18,17 +18,7 @@ Use this as the default ATVM automation run-status template for:
- scope of this run: `<batch or run scope>`
**TEST FLOW:**
- 1. Verifying set up
- 2. Power on and obtain ip address and host name
- 3. Uninstall cmc if still exist
- 4. Setting up disk
- 5. Copy cmc install command from GUI
- 6. Install cmc
- 7. Create migration session
- 8. Tracking Changes
- 9. Trigger cmotion and do I/O test before actual cutover
- ...
- 22. Power off
- <template-specific numbered steps>
**SUMMARY:**
@@ -82,7 +72,28 @@ Use this as the default ATVM automation run-status template for:
- Keep `Detail` concise.
- Put broader context under `NOTES:`, not in the host table.
- `COVERAGE:` should describe what the run was intended to cover without listing target hosts.
- `TEST FLOW:` should describe the generic numbered run flow once for the whole test, not per host.
- `TEST FLOW:` should describe the template-specific numbered run flow once for the whole test, not per host.
- The watcher resolves `TEST FLOW:` from the run template name.
- `cmc-e2e` currently uses this flow:
- `1. Verifying set up`
- `2. Power on and obtain ip address and host name`
- `3. Uninstall CMC if still exists`
- `4. Setting up disk`
- `5. Copy CMC install command from GUI`
- `6. Install CMC`
- `7. Create migration session`
- `8. Tracking Changes`
- `9. Trigger cmotion and do I/O test before actual cutover`
- `10. Verify migration remains healthy during I/O activity`
- `11. Prepare for cutover`
- `12. Stop application / stop test I/O`
- `13. Run final sync`
- `14. Confirm destination is fully up to date`
- `15. Perform cutover`
- `16. Validate destination host / disk state`
- `17. Run post-cutover checks`
- `18. Power off`
- See `/home/aw/code/cds/atvm/docs/automation/examples.md` for `cmc-e2e` examples.
- Resolve kernel values by cross-referencing hostnames against `/home/aw/code/cds/atvm/inventory/vm-inventory.md`.
- If no kernel value can be verified from `vm-inventory.md`, use `unknown`.
- Use the same template for Mattermost and local operator-visible status output.