Files

T

vh c27761f608 servers/pfi-pve: full VM/CT enumeration from live qm list

Previously a partial list "from vzdump logs + servers/ dirs". Replaced
with the full output of `qm list` on pfi-pve (2026-05-14), cross-
referenced against `servers/`. VMs that have a server dir are
annotated with the path; ones that don't are flagged "not yet in
`servers/` inventory" so the gap is discoverable.

Resolved:
- VM 100 = pbs-ana (was "VM (TBD)" in prior version)
- VM 106 = corviduo-dev (added 2026-05-12; was missing from the list)

Surfaced (new findings, not yet inventoried):
- VM 101 — PFI-ANA-DC (Active Directory domain controller)
- VM 103 — PFI-SlaveBot (purpose unclear from name alone)
- VM 104 — PFI-Mongo (MongoDB host, separate from pfi-postgres)

The three new-to-inventory VMs deserve `servers/<name>/` directories
with READMEs, but that's a follow-up — creating new inventory entries
is out of tend-docs scope.

2026-05-14 15:38:34 -07:00

2.8 KiB

Raw Blame History

pfi-pve

Proxmox VE hypervisor for the Anaheim colo (pve.phasefinal.com). Hosts every VM in the PFI-ANA cluster.

Network

LAN IP: 10.250.250.31 (in-band, OS-side)
iDRAC (OOB): 10.250.250.30 — Dell iDRAC web UI at https://10.250.250.30/ (homepage card: PFI-r750xs-iDRAC)
FQDN: pve.phasefinal.com
Web UI: https://10.250.250.31:8006
SSH: root@pfi-pve (key auth; ssh-target file uses the hostname)

Hardware

Chassis: Dell PowerEdge R750xs (2U rackmount)
CPU: Intel Xeon Silver 4310 @ 2.10 GHz
RAM: 188 GB
Kernel: 6.8.12-8-pve (Proxmox 8.x)
Storage: local pve-root at 65G (49% used) + pve LVM pool for VM disks

What it runs

The VMs/CTs in docs/pfi/proxmox-vms.md live here. Full enumeration as of 2026-05-14 (via qm list on the hypervisor):

VM 100 — pbs-ana (Proxmox Backup Server; 10.250.50.90) — servers/pbs-ana/
VM 101 — PFI-ANA-DC — Active Directory domain controller; not yet in servers/ inventory
VM 102 — ana-docker (PFI-ANA-Docker) — servers/ana-docker/
VM 103 — PFI-SlaveBot — not yet in servers/ inventory (purpose TBD)
VM 104 — PFI-Mongo — MongoDB host; not yet in servers/ inventory
VM 105 — pfi-postgres (PFI-Postgres; PGDATA on local VM disk as of 2026-04-23 migration off ana-nas NFS) — servers/pfi-postgres/
VM 106 — corviduo-dev (Worldtree-team dev VM, PFI-hosted) — servers/corviduo-dev/
VM 107 — pfi-pteradactyl (game panel) — servers/pfi-pteradactyl/
VM 110 — pfi-ana-webhost — servers/pfi-ana-webhost/
VM 111 — pfi-tacticalrmm — servers/pfi-tacticalrmm/
CT 109 — ana-nas (Debian LXC serving NFS/SMB; bind-mounts from ospool; data-serving SPOF — see memory/incident_ana_nas_spof.md) — servers/ana-nas/
CT 112 — ana-filebot (file-task automation) — servers/ana-filebot/
CT 113 — ana-wg (WireGuard VPN) — servers/ana-wg/

ana-ml2 (10.250.50.54) is a separate bare-metal Supermicro box, not on this hypervisor. sfsrv-ana (10.250.250.115) runs on a separate Dell R630, also not on this hypervisor.

Refresh state

scripts/refresh-server-info.sh pfi-pve

The snapshot captures host/hardware/filesystem/network/ports but not VM-level detail (server_inspect.sh targets Docker hosts). Running qm list, pvesh get /cluster/resources, and zpool list -v manually is the current way to audit VMs and storage. A Proxmox-flavored inspect script is a future improvement.

Placement rule

This is a hypervisor, not a target for Docker stacks. Add new workloads by standing up VMs here (or on ana-docker / ana-ml2, whichever fits) rather than deploying containers directly on the PVE host.

2.8 KiB Raw Blame History