Files
cds-ai/cdsmcp/docs/cmc-install-reference.md
anthony.wen c0004c1dff Document separate Linux and Windows ATVM target credentials
- add explicit Windows ATVM guest credential references alongside the existing Linux target defaults
- update the ATVM automation guide and AGENTS rules so Linux SSH uses ATVM_TARGET_* while Windows guest access uses ATVM_WINDOWS_TARGET_*
- update the CDS MCP CMC install and VMware workflow docs to distinguish Linux and Windows credential usage for the shared ATVM target IP
- update the VM lookup reference so common VM credentials list both Linux and Windows target variables
2026-03-26 08:33:41 -04:00

1.7 KiB

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)

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.

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"

Uninstall (Linux)

curl https://get.cirrusdata.cloud/install-cmc | bash -s -- -uninstall

Uninstall (Windows)

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.