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

cdsmcp: add direct ESX VM hardware workflow guide

Browse Source 
Add a dedicated ESX VM guide for read-first hardware change workflows,
including disk creation, datastore VMDK attachment, and PCI passthrough
assignment.

Update the existing lookup/assignment runbook and top-level docs to
reference the new guide and require explicit reporting of VM name
mismatches and missing datastore directories before any change.
This commit is contained in:
anthony.wen
2026-04-24 11:09:13 -04:00
parent 2e25c2ae2b
commit a02227fbe5
4 changed files with 62 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
cdsmcp/docs/vm-lookup-and-assignment.md
View File

@@ -26,6 +26,7 @@ This file covers vCenter VM lookup responses and the workflow for assigning exis
- then wait for explicit approval before making any changes
- Always log into vCenter `192.168.0.201`.
- Find the specified VM and verify the ESXi host it is currently running on.
- If the requested VM name is not present exactly as given, search for the closest live inventory name and report the mismatch before planning any change.
- Default expected ESXi host is `192.168.1.165`, but always verify live placement before planning changes.
- Always identify and report the datastore where the VM is stored before planning disk attachment.
- Unless the operator explicitly specifies alternatives, default to these PCI passthrough FC adapters:
@@ -37,8 +38,10 @@ This file covers vCenter VM lookup responses and the workflow for assigning exis
- `atvm-DISK_2.vmdk`
- Do not substitute any other disks if either default or operator-specified disk cannot be found.
- If the specified adapters or specified disks cannot be found, do nothing and report that nothing will be assigned.
- For these requests, never substitute a different datastore directory when `atvm-DISKS` is missing.
- Before any assignment action, always provide a summary of:
- the VM found
- any name mismatch between requested VM name and live inventory VM name
- the ESXi host
- the datastore
- whether `vmhba7` and `vmhba8` were found and are usable