Files
vh 91bda3c480 fv-ml1: complete the cutover — rename, renumber, DNS, and the LiteLLM repoint
The box is physically at Fountain Valley, renamed, renumbered onto 10.251/16,
and serving inference again. This lands the repo half of that.

Host: hostname ana-ml2 -> fv-ml1, pinned to 10.251.50.54 by a dnsmasq
reservation so the address the runbook, DNS and LiteLLM all assume is the
address it actually has. Its headscale node is renamed too.

The sweep ran from scripts/fv-ml1-rename-sweep.sh, whose allowlist is the
reason this diff touches current-state files and not the record. Dated
persistent-memory entries, archival-memory and incident notes still say
ana-ml2 in 31 and 62 places respectively, because that is what the box was
when those things happened. Rewriting them would make the history lie.

LiteLLM was the load-bearing piece and needed more than the api_base sed the
runbook describes. Twenty api_base entries repointed, but a grep-and-verify
pass also caught a LIVE pass_through_endpoints target for the scalar-judge
reward route still on the old address -- an api_base-only substitution would
have left it dead. Four prose references describing current state were
repointed as well; one historical note recording where a hand-test was run
is deliberately left pointing at 10.250.50.54.

Two facts in the server tables were wrong and are corrected here. The site is
Fountain Valley, not Anaheim. And the box has FOUR RTX PRO 6000 Blackwell
Max-Q, not two -- verified by nvidia-smi -L and independently by PCI
enumeration of four GB202GL devices. That is 391 GB of VRAM rather than 196,
which changes what fits on it.

DNS: fv-ml1, fv-ml1-bmc and fv-gw added under the fv site via the piggyback
approach, scriberr re-homed, and the ana-ml2 records removed. Applied to all
three resolvers. The BMC record carries a warning that its 802.1q VLAN tag
must stay disabled -- it shipped tagging VLAN 250 into an untagged port,
which made it invisible to every network-side diagnostic and is the reason
it appeared dead through several cable changes.

Verified end to end: summarizer and sec both answer through the Anaheim
gateway across the mesh to FV seats on different ports.
2026-09-12 22:00:50 -07:00

5.3 KiB
Raw Permalink Blame History

PFI-ANA Proxmox guest inventory (pfi-pve)

Refreshed 2026-09-06 04:47Z from live qm list, pct list, /etc/pve/*/N.conf and guest-agent IPs. Earlier versions of this file described guests that no longer exist (VM 100 as the TrueNAS box, VM 106 as "PFI-Tailscale", VM 108 "PFI-ANA--DEV"); this version is the live state.

Hypervisor: pfi-pve — Dell PowerEdge R750xs, Xeon Silver 4310 (48 threads), 188 GB, Proxmox VE 8.3.5, https://10.250.250.31:8006, ssh infra-ops@10.250.250.31 (NOPASSWD sudo, since 2026-09-06) or root@. iDRAC https://10.250.250.30.

Storage:

id type backs notes
ospool zfspool, 2×mirror (bays 0–3), 10.9T raw every VM boot disk and every CT rootfs except pbs-ana the pool that boots the site; also holds ospool/naspool-evac (parked copy from the 2026-09-06 rebuild, to be destroyed)
NASPool zfspool, raidz2 ×6 (bays 4–8, 11), 21.7T usable backup / bulk tier: backupStore (PBS-ANA datastore, restic repos), pve-VMStorage, db, docker, webdav rebuilt 2026-09-06 (docs/runbooks/pfi-pve-naspool-rebuild.md); bays 9/10 dead (backplane), drives in them = cold spares
naspool-vmstorage dir on /NASPool/pve-VMStorage ISOs, templates, legacy vzdump (newest-per-guest only) was pve-truenas until 2026-09-06
local-lvm lvmthin pbs-ana's boot disk
local dir ISOs
pbs-ana pbs at 10.250.50.90 vzdump jobs (03:00 all guests except 100,109; 22:00 CT 109) datastore lives on NASPool/backupStore via ana-nas NFS

Network: all guests on vmbr0 VLAN tag 50 (10.250.50.0/24), firewall enabled on every NIC. Linux = virtio, Windows = e1000. CTs take DHCP (reserved).

Virtual machines

VMID name IP vCPU (sockets×cores) RAM disk OS onboot / startup role
100 pbs-ana 10.250.50.90 4 (1×4, x86-64-v2-AES) 8 G 32G local-lvm Debian 12 yes / — Proxmox Backup Server, fleet primary. servers/pbs-ana/
101 PFI-ANA-DC 10.250.50.60 12 (2×6, host) 24 G 240G ospool + EFI + TPM2 Windows 11, q35, OVMF yes / order 5, up 120s Active Directory domain controller
102 PFI-ANA-Docker 10.250.50.70 8 (2×4, x86-64-v2-AES) 16 G 250G ospool Debian yes / order 4 ana-docker: LiteLLM gateway, gitea, Langfuse, AdGuard, Beszel/Dozzle hubs, rest-server-ana, backrest. servers/ana-docker/
103 PFI-SlaveBot 10.250.50.151 8 (2×4, host) 8 G 256G ospool (ide0) Windows 10, i440fx yes / — purpose undocumented; not in servers/
104 PFI-Mongo 10.250.50.81 8 (2×4, host) 8 G 256G ospool Linux yes / order 3, up 60s MongoDB; not in servers/
105 PFI-Postgres 10.250.50.80 16 (4×4) 8 G 80G ospool Debian 11 yes / order 3, up 60s shared Postgres (vaultwarden/gitea/paperless); PGDATA local since 2026-04-23. servers/pfi-postgres/
106 corviduo-dev 10.250.50.152 8 (2×4, x86-64-v2-AES) 8 G 80G ospool Debian 13 yes / order 10 Worldtree-team dev VM, PFI-hosted. servers/corviduo-dev/
107 PFI-Pteradactyl 10.250.50.55 8 (2×4, host) 8 G 256G ospool Debian 11 yes / — Pterodactyl game panel. servers/pfi-pteradactyl/
110 PFI-ANA-Webhost 10.250.50.52 16 (4×4) 4 G (balloon 1 G) 250G ospool Debian 11 yes / order 30, up/down 120s web workload. servers/pfi-ana-webhost/
111 pfi-tacticalrmm 10.250.50.57 16 (4×4) 8 G 256G ospool Linux yes / order 20 TacticalRMM. servers/pfi-tacticalrmm/

All VMs have the QEMU guest agent enabled.

Containers

CTID hostname IP cores RAM rootfs privileged onboot / startup role
109 ana-nas 10.250.50.50 4 2 G 80G ospool yes (apparmor unconfined, all devices) yes / order 1, up 45s NFS/SMB server straight off the ZFS pools — bind-mounts /ospool/backup and every NASPool/* dataset under /mnt/…. Data-serving SPOF. servers/ana-nas/
112 ana-filebot 10.250.50.53 4 2 G 80G ospool yes (same binds as 109) yes / order 10 file-task automation. servers/ana-filebot/
113 ana-wg 10.250.50.252 (+ wg0 10.30.10.1) 4 2 G 8G ospool no (nesting) yes / order 2 WireGuard remote-access endpoint, UDP 31337 via FortiGate VIP. servers/ana-wg/

Startup order (host boot)

order guest delay
1 CT 109 ana-nas up 45s
2 CT 113 ana-wg —
3 VM 104 PFI-Mongo, VM 105 PFI-Postgres up 60s
4 VM 102 PFI-ANA-Docker —
5 VM 101 PFI-ANA-DC up 120s
10 VM 106 corviduo-dev, CT 112 ana-filebot —
20 VM 111 pfi-tacticalrmm —
30 VM 110 PFI-ANA-Webhost up/down 120s
unordered VM 100 pbs-ana, VM 103, VM 107 onboot=1, no sequencing

Reverse this for a graceful host shutdown (done 2026-09-05 for the PERC swap).

Resource summary

vCPU RAM disk
10 VMs 108 100 G 2,180 G
3 CTs 12 6 G 168 G
total 120 on 48 threads (2.5× overcommit) 106 G of 188 G on ospool 547 G actually allocated (thin)

Not on this hypervisor

fv-ml1 (10.251.50.54) is bare-metal Supermicro; sfsrv-ana (10.250.250.115) is the SureFire client's own Dell R630; pfi-gx10 is at NH3.