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

Document Windows SSH-based CMC workflow for CDS MCP

Browse Source 
- update the CDS MCP CMC install reference to prefer SSH plus PowerShell for Windows guest execution instead of VMware guest operations
- document the Windows install-state check and uninstall-then-reinstall pattern so it matches the Linux CMC preparation flow
- update the VMware MigrateOps guide to treat Windows CMC preparation as an SSH-based workflow using ATVM_WINDOWS_TARGET_* credentials
- update the CDS MCP README and AGENTS guidance so the Windows guest execution default is explicit
This commit is contained in:
anthony.wen
2026-03-26 08:47:53 -04:00
parent c0004c1dff
commit b19d6a912e
4 changed files with 19 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
cdsmcp/docs/vmware-migrateops-guide.md
View File

@@ -24,6 +24,7 @@ This file is for workflow guidance only. Do not add specific run examples here.
- When the operator refers to `192.168.3.191`, assume ATVM target SSH access should ignore host key mismatch by default with `-o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null`.
- When the operator refers to `192.168.3.191` for Linux SSH access, source `/home/aw/code/cds/.env.credentials.local` and use `ATVM_TARGET_USER` plus `ATVM_TARGET_PASSWORD` unless the operator explicitly overrides them.
- When the operator refers to `192.168.3.191` for Windows guest access, source `/home/aw/code/cds/.env.credentials.local` and use `ATVM_WINDOWS_TARGET_USER` plus `ATVM_WINDOWS_TARGET_PASSWORD` unless the operator explicitly overrides them.
- For Windows guest command execution, prefer SSH + PowerShell on the guest instead of VMware guest operations unless the operator explicitly requests otherwise.
## Related References
- VM lookup, datastore reporting, and FC/disk assignment:
@@ -35,7 +36,7 @@ This file is for workflow guidance only. Do not add specific run examples here.
- Use `/home/aw/code/cds/cdsmcp/templates/vmw.yaml` as the starting template.
- Default sequence for requested source machine:
- clean CDC state for that machine
- reinstall CMC Linux on that machine
- reinstall CMC on that machine
- perform migration preflight and operation create
- If user provides a client name, replace consistently:
- `config.system_name`
@@ -64,6 +65,13 @@ This file is for workflow guidance only. Do not add specific run examples here.
- Destination datastore/host/network resolve in vCenter.
- `source_nic` discovered via SSH from source host.
## CMC Preparation Rule
- For Linux sources, use the Linux SSH credential path and the Linux install/uninstall reference.
- For Windows sources, use SSH to the guest with `ATVM_WINDOWS_TARGET_USER` and `ATVM_WINDOWS_TARGET_PASSWORD`.
- For Windows sources, check whether CMC is already installed before install.
- If Windows CMC is already present, uninstall first and then reinstall using the Windows PowerShell installer command.
- Do not treat VMware guest operations as the default Windows execution path.
## Post-Migration Validation and Cleanup Pattern
- Validate destination login before cleanup:
- get destination guest IP from vCenter