vh
2033d3da65
VMIDs 100 (PFI-ANA-TRUENAS), 106 (PFI-Tailscale), 108 (PFI-ANA-DEV) retired. Backup job extended to cover 107 (PFI-Pteradactyl) and the previously-missing LXCs 109 (ana-nas), 112 (ana-filebot), 113 (ana-wg). All 11 remaining guests now covered — no backup gaps.
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
- FQDN:
pve.phasefinal.com - Web UI:
https://10.250.250.31:8006 - SSH:
root@pfi-pve(key auth;ssh-targetfile uses the hostname)
Hardware
- 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 in docs/pfi/proxmox-vms.md live here — VM 100 (PFI-ANA-TRUENAS, now Debian NFS/SMB), VM 101 (DC), VM 102 (PFI-ANA-Docker = ana-docker), 103–111 (Mongo, Postgres, Tailscale, Pteradactyl, Webhost, tacticalrmm, etc.).
ana-ml2 (10.250.50.54) is a separate bare-metal box, 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.