anthony.wen
a02227fbe5
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.
64 lines
3.1 KiB
Markdown
64 lines
3.1 KiB
Markdown
# VM Lookup And Assignment
|
|
|
|
This file covers vCenter VM lookup responses and the workflow for assigning existing disks and PCI passthrough FC adapters to a VM.
|
|
|
|
## Cluster Scope Rule
|
|
- Only work under cluster `QACL-ATVMCypressONLY` unless explicitly told otherwise.
|
|
|
|
## Ignore VMs
|
|
- `vCLS-bf0ec6f6-c7e2-4383-b11e-9c97cec7ed44`
|
|
- `vCLS-e5b3c60e-6a1c-46a6-8357-191fc0ab8e14`
|
|
|
|
## IP Lookup Rule
|
|
- If asked about an IP address, only check powered-on VMs.
|
|
|
|
## VM Lookup Response Rule
|
|
- Unless the user explicitly asks otherwise, return VM lookup/list results only from cluster `QACL-ATVMCypressONLY`.
|
|
- For vCenter VM lookup requests, always report:
|
|
- VM name
|
|
- datastore name
|
|
- VM notes/annotation
|
|
- include power state and IP when available
|
|
|
|
## VM Disk And FC Assignment Workflow
|
|
- When asked to assign existing disks and PCI passthrough FC adapters to a specified VM, treat the request as a two-step workflow:
|
|
- first gather and report findings
|
|
- 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:
|
|
- `vmhba7` (`0000:85:00.0`)
|
|
- `vmhba8` (`0000:85:00.1`)
|
|
- Do not substitute any other PCI FC passthrough adapters if either default or operator-specified adapter cannot be found.
|
|
- Unless the operator explicitly specifies alternatives, default to these existing disks from the VM's datastore under the `atvm-DISKS` directory:
|
|
- `atvm-DISK_1.vmdk`
|
|
- `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
|
|
- whether `atvm-DISK_1.vmdk` and `atvm-DISK_2.vmdk` were found under `atvm-DISKS`
|
|
- exactly what would be assigned
|
|
- Never perform the assignment step until the operator explicitly approves after seeing that summary.
|
|
|
|
## Common VM Credentials
|
|
- Source `/home/aw/code/cds/.env.credentials.local`
|
|
- Linux username: `ATVM_TARGET_USER`
|
|
- Linux password: `ATVM_TARGET_PASSWORD`
|
|
- Windows username: `ATVM_WINDOWS_TARGET_USER`
|
|
- Windows password: `ATVM_WINDOWS_TARGET_PASSWORD`
|
|
|
|
## Status Output Format (Power-Off/Revert/Power-On)
|
|
- `VM [vm name] was poweredOn, so I powered it off` (or `already poweredOff`)
|
|
- `Snapshot rollback completed`
|
|
- `VM [vm name] powered back on successfully`
|
|
- `Current IP: <ip>`
|