Files
cds-ai/cdsmcp/AGENTS.md
anthony.wen d989c8a071 Document default FC and disk assignment workflow for ATVM VMs
Update the VMware runbook to describe the default VM attachment workflow for assigning FC passthrough adapters vmhba7 and vmhba8 plus datastore disks atvm-DISK_1.vmdk and atvm-DISK_2.vmdk, with mandatory live verification, pre-action summary, explicit approval, and no-substitution behavior unless the operator specifies alternatives.
2026-03-18 19:40:32 -04:00

3.0 KiB

AGENTS.md

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

Files

  • esxvm.md: index file only; points to guide and run-learnings docs.
  • esxvm-guide.md: authoritative workflow/rules/checklists/default behavior.
  • esxvm-runs.md: run-specific learnings, only when a run adds new information.
  • vmw.yaml: base template for MIGRATEOPS_VMWARE_COMPUTE operations.

Source Of Truth

  • Use esxvm-guide.md for how to execute runs.
  • Use vmw.yaml as the starting operation template.
  • Treat esxvm-runs.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 esxvm-guide.md (integration, access node, destination name, datastore/host/network, source NIC).
  4. Create MigrateOps from vmw.yaml with request-specific replacements.
  5. Monitor continuously and auto-approve cutover unless user requests manual approval.
  6. After terminal state:
  • validate destination login (poll guest IP if needed),
  • 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 user explicitly before deleting destination VM; never delete without same-run confirmation.

VM Lookup Requirement

  • Unless user explicitly asks otherwise, scope VM lookup/list responses to cluster QACL-ATVMCypressONLY.
  • For vCenter VM lookup requests, always include datastore name and VM notes/annotation in the response.

VM Disk And FC Assignment Requirement

  • For requests to assign disks and PCI passthrough FC adapters to a VM, use the workflow in esxvm-guide.md.
  • Always verify the VM, live ESXi host, and datastore first.
  • Default expected host is 192.168.1.165, but verify live placement before planning.
  • Unless the operator explicitly specifies alternatives, default to planning these FC adapters:
  • vmhba7 (0000:85:00.0)
  • vmhba8 (0000:85:00.1)
  • Unless the operator explicitly specifies alternatives, default to planning these existing datastore disks:
  • atvm-DISK_1.vmdk
  • atvm-DISK_2.vmdk
  • The disks must be located in the same datastore as the VM under the atvm-DISKS directory.
  • If the default or operator-specified adapters or disks are missing, do nothing and report that no assignment will be performed.
  • Always provide a read-only summary of findings and planned assignment, then wait for explicit approval before any change.

Update Rules

  • Update esxvm-guide.md only when workflow/rules/default behavior changes.
  • Update esxvm-runs.md only when a run reveals a new learning/failure pattern/required check.
  • Keep esxvm.md as a lightweight index.

Environment Defaults

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