Files
cds-ai/atvm/inventory/infrastructure.md
anthony.wen a26fa29912 Document live vCenter ATVM datastore selection
- map AutomatedTest-VMBootImg-Gold to gold and Gold-2 to gold-2
- require live vCenter placement checks for explicit VM lists
- stop mixed gold/gold-2 requests before planning ATVM runs
- return hostname-only datastore inventories by default
- tell the operator about the vCenter placement check before showing run commands
- clarify that repo inventory files are not the source of truth for current datastore membership
2026-04-15 08:45:52 -04:00

70 lines
2.6 KiB
Markdown

# ATVM Infrastructure
This file organizes the main infrastructure reference that was previously embedded in the long-form ATVM notes.
Tracked docs should reference `/home/aw/code/cds/.env.credentials.local` for secret values instead of storing them inline.
## Storage / Appliance
- Primary DGS Phoenix Server: `192.168.1.172`
- Replica DGS Phoenix Server: `192.168.1.89`
- Primary DGS web login:
- `DGS_PRIMARY_USER / DGS_PRIMARY_PASSWORD`
- The preserved detailed storage and appliance notes remain in:
- `archive/imported-notes/cypress-automation-for-cmc.md`
## VMware
- Active vCenter Server Appliance: `192.168.0.201`
- vCenter login:
- `VCENTER_USER / VCENTER_PASSWORD`
- Primary ESXi hosts:
- `192.168.1.165`
- `192.168.1.166`
- Primary ATVM boot datastores:
- `AutomatedTest-VMBootImg-Gold` -> `gold` -> `cypress.atvm-config-gold.ts`
- `AutomatedTest-VMBootImg-Gold-2` -> `gold-2` -> `cypress.atvm-config-gold-2.ts`
- Current VM membership for those datastores should be queried from live vCenter when needed, not stored as a maintained repo-side live reference list.
- ATVM datastore placement rule for explicit VM-list test requests:
- all requested VMs must resolve to one datastore family only
- do not run a mixed request spanning both `AutomatedTest-VMBootImg-Gold` and `AutomatedTest-VMBootImg-Gold-2`
- if the request is mixed, stop and report the per-datastore VM split so the operator can correct the list
- ESXi `192.168.1.165`:
- SSH: `ESXI_HOST_1_USER / ESXI_HOST_1_PASSWORD`
- IPMI: `ESXI_HOST_1_IPMI_USER / ESXI_HOST_1_IPMI_PASSWORD`
- ESXi `192.168.1.166`:
- SSH: `ESXI_HOST_2_USER / ESXI_HOST_2_PASSWORD`
- IPMI: `ESXI_HOST_2_IPMI_USER / ESXI_HOST_2_IPMI_PASSWORD`
- Legacy VMware environment details are preserved in the archived notes.
## ATVM Controller Host
- Controller host reference:
- `atvm-cypress-vm`
- `atvm-cypress-vm-1`
- Controller IP:
- `192.168.3.190`
- Controller credentials:
- `ATVM_CONTROLLER_USER / ATVM_CONTROLLER_PASSWORD`
- `ATVM_CONTROLLER_ALT_USER / ATVM_CONTROLLER_ALT_PASSWORD`
- Current noted controller variants:
- `atvm-cypress-vm`
- `atvm-cypress-vm-1`
## Offline Repository Host
- Repository host:
- `linux-repo-vm`
- Repository IP:
- `192.168.3.199`
- Repository credentials:
- `ATVM_REPO_USER / ATVM_REPO_PASSWORD`
- Repository content families include:
- RedHat
- Debian
- Suse
## Detailed Source Sections
- Storage Array / Appliance
- VMware Hosts
- ATVM Cypress Host
- Offline DVD Linux Repository
These sections are preserved in full at:
- `archive/imported-notes/cypress-automation-for-cmc.md`