anthony.wen
b19d6a912e
- 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
45 lines
2.3 KiB
Markdown
45 lines
2.3 KiB
Markdown
# CMC Install Reference
|
|
|
|
This file contains the CMC install, uninstall, and reinstall fallback reference used by the CDS MCP VMware workflow.
|
|
|
|
## Default Project Rule
|
|
- Default project: `Skidamarink`
|
|
- Source `/home/aw/code/cds/.env.credentials.local` and use `CMC_GCSTAGE_REGISTRATION_CODE`
|
|
- Default endpoint: `portal.gcstage.cloud.nonprod.cirrusdata.com:443`
|
|
- Use a different project code only when the user explicitly requests it in that run.
|
|
|
|
## Skidamarink Install (Linux)
|
|
```bash
|
|
source /home/aw/code/cds/.env.credentials.local
|
|
curl https://get.cirrusdata.cloud/install-cmc | bash -s -- -rgc "$CMC_GCSTAGE_REGISTRATION_CODE" -gce portal.gcstage.cloud.nonprod.cirrusdata.com:443 -pkg-mode PRE_RELEASE
|
|
```
|
|
|
|
## Skidamarink Install (Windows)
|
|
Source `/home/aw/code/cds/.env.credentials.local` first so `CMC_GCSTAGE_REGISTRATION_CODE` is present in the PowerShell environment, and use `ATVM_WINDOWS_TARGET_USER` plus `ATVM_WINDOWS_TARGET_PASSWORD` for Windows guest access unless the operator explicitly overrides them.
|
|
Prefer SSH to the Windows guest and execute the PowerShell command there instead of relying on VMware guest operations.
|
|
|
|
```powershell
|
|
iex "& { $(irm https://get.cirrusdata.cloud/install-cmc-win) } -rgc $env:CMC_GCSTAGE_REGISTRATION_CODE -gce portal.gcstage.cloud.nonprod.cirrusdata.com:443 -pkg-mode PRE_RELEASE"
|
|
```
|
|
|
|
## Windows Reinstall Pattern
|
|
- Before install or reinstall, connect over SSH with `ATVM_WINDOWS_TARGET_USER` and `ATVM_WINDOWS_TARGET_PASSWORD`.
|
|
- Check whether CMC is already installed before deciding on the next action.
|
|
- If CMC is already installed, uninstall first, then run the Windows install command again.
|
|
- Use the same registration code and endpoint defaults as the Linux flow.
|
|
- Prefer direct SSH + PowerShell execution for both the install and uninstall commands.
|
|
|
|
## Uninstall (Linux)
|
|
```bash
|
|
curl https://get.cirrusdata.cloud/install-cmc | bash -s -- -uninstall
|
|
```
|
|
|
|
## Uninstall (Windows)
|
|
```powershell
|
|
iex "& { $(irm https://get.cirrusdata.cloud/install-cmc-win) } -uninstall"
|
|
```
|
|
|
|
## CMC Reinstall Fallback (RHEL 10)
|
|
- If installer-based reinstall fails due repo metadata/download errors, use cached local `mtdi-daemon` and `galaxy-migrate` RPMs, start services, enforce `galaxy_complete_endpoint`, then manually register.
|
|
- Do not continue MigrateOps create until the source host is visible as connected in CDC.
|