anthony.wen/cds-ai
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
0405c09987493d36f0e757ae65c180c42c5d9734
cds-ai/cdsmcp/AGENTS.md
anthony.wen 0405c09987 Reorganize cdsmcp workspace into docs, templates, and artifacts 
Restructure the cdsmcp folder to separate operator guidance, reusable templates, and runtime artifacts into clearer top-level areas.

Move the VMware migration guide and run learnings into docs/, move vmw.yaml into templates/, move the existing log into artifacts/logs/, replace the old index file with a README, and split the former monolithic guide into focused documents for VMware MigrateOps workflow, VM lookup and FC/disk assignment, and CMC install reference.

Update internal references so the reorganized layout remains coherent without changing the underlying operational guidance.
2026-03-21 20:57:14 -04:00

2.6 KiB
Raw Blame History

AGENTS.md

This folder contains the VMware/vCenter + MigrateOps runbook for CDS MCP workflows.

Workspace Layout

  • README.md
    • top-level navigation
  • docs/vmware-migrateops-guide.md
    • authoritative VMware compute migration workflow
  • docs/vm-lookup-and-assignment.md
    • VM lookup, datastore reporting, and FC/disk assignment workflow
  • docs/cmc-install-reference.md
    • CMC install, uninstall, and reinstall fallback reference
  • docs/run-learnings.md
    • run-specific learnings only when a run adds new information
  • templates/vmw.yaml
    • base template for MIGRATEOPS_VMWARE_COMPUTE operations
  • artifacts/logs/
    • runtime log artifacts kept separate from operator guidance

Source Of Truth

  • Use docs/vmware-migrateops-guide.md for how to execute VMware compute migration runs.
  • Use docs/vm-lookup-and-assignment.md for VM lookup responses and FC/disk assignment requests.
  • Use docs/cmc-install-reference.md for CMC install/uninstall commands and fallback reinstall notes.
  • Use templates/vmw.yaml as the starting operation template.
  • Treat docs/run-learnings.md as evidence/history, not baseline procedure.

Required Run Pattern

  1. Confirm source VM in vCenter and power state before IP/SSH actions.
  2. Prepare source host (CDC cleanup + CMC reinstall/registration) and verify source is connected in CDC.
  3. Validate preflight requirements from docs/vmware-migrateops-guide.md.
  4. Create MigrateOps from templates/vmw.yaml with request-specific replacements.
  5. Monitor continuously and auto-approve cutover unless the user requests manual approval.
  6. After terminal state:
  • validate destination login,
  • archive operation,
  • run offline-host cleanup loop until source/helper cleanup conditions are satisfied,
  • provide final read-only status listing for source/destination/access/helper across CDC and vCenter.
  1. Ask the user explicitly before deleting the destination VM; never delete without same-run confirmation.

Environment Defaults

  • vCenter: 192.168.0.201
  • Cluster scope: QACL-ATVMCypressONLY unless user overrides
  • Default CDC project: Skidamarink
  • Default access node: atvm-linux-h2h
  • Default ATVM target reference: 192.168.3.191

Update Rules

  • Update docs/vmware-migrateops-guide.md only when migration workflow/default behavior changes.
  • Update docs/vm-lookup-and-assignment.md only when lookup/assignment workflow behavior changes.
  • Update docs/cmc-install-reference.md only when install or reinstall reference behavior changes.
  • Update docs/run-learnings.md only when a run reveals a new learning/failure pattern/required check.
Reference in New Issue View Git Blame Copy Permalink