vh
60367b307f
Bundles the inventory expansion since 2026-04-22:
- New host dirs (READMEs + ssh-target where dir name doesn't resolve):
ana-nas, ana-wg, esh-vm-db, nh3-nas, pbs-ana, pbs-nh3.
- New PFI VM snapshots (registered + key-installed 2026-04-23):
ana-filebot, pfi-ana-webhost, pfi-postgres, pfi-pteradactyl,
pfi-tacticalrmm, sf-ana-container, sfsrv-ana (system + proxmox).
- servers/irv-ml1: ONBOARDING.md (the first-time setup notes from when
the host was brought into the fleet) + ssh-target (10.100.79.3 over
the WG tunnel — name doesn't DNS-resolve from this workstation).
- servers/{ana-ml2,pfi-pve,sf-r630}/README.md: updates to capture BMC
IPs, the iDRAC vs OS hostname distinction (sf-r630 hardware =
sfsrv-ana OS), and the ana-ml2 Supermicro BMC (10.250.250.50,
distinct from the Dell R750xs iDRAC).
- configs/homepage/docker.yaml: irv-ml1-docker provider added so
homepage auto-discovers irv-ml1's stacks over the WG tunnel.
- docs/orientation.md: narrative fleet overview written for fresh
Claude sessions — sites, backup architecture, governing principles,
gotchas, where-to-look guide. Pointed at from CLAUDE.md.
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-targetfile 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-rootat 65G (49% used) +pveLVM pool for VM disks
What it runs
The VMs/CTs in docs/pfi/proxmox-vms.md
live here. Known as of 2026-04-23 (from vzdump logs + servers/
dirs; not exhaustive):
- VM 102 —
ana-docker(PFI-ANA-Docker) - VM 105 —
pfi-postgres(PFI-Postgres; PGDATA on NFS from ana-nas) - VM 107 —
pfi-pteradactyl(game panel) - VM 110 —
pfi-ana-webhost - VM 111 —
pfi-tacticalrmm - VM (TBD) —
pbs-ana(Proxmox Backup Server; 10.250.50.90) - CT 109 —
ana-nas(Debian LXC serving NFS/SMB; bind-mounts from ospool; data-serving SPOF — seememory/incident_ana_nas_spof.md) - CT 112 —
ana-filebot(file-task automation) - CT 113 —
ana-wg(WireGuard VPN)
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.