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.
sf-r630
SureFire-client physical server at the Anaheim colo — Dell PowerEdge R630. PFI-managed under the hosting agreement (hardware + OS ops).
This directory documents the hardware / iDRAC side only. The OS
running on this box is tracked separately as
servers/sfsrv-ana/ — Proxmox VE at
10.250.250.115. Refer to that for OS-level snapshots, SSH access,
and backup coverage.
Client context
- Client: SureFire
- PFI role: full-service managed host (iDRAC + Proxmox)
Network
- iDRAC BMC:
10.250.250.110(dedicated OOB management NIC)- Web UI: https://10.250.250.110/ (currently 404s; use the vSphere-style Redfish API or racadm from iDRAC shell for out-of-band ops)
- Homepage monitors this via ICMP ping rather than HTTP
- OS-side (Proxmox VE): see
servers/sfsrv-ana/—10.250.250.115
Hardware
- Type: Physical Dell PowerEdge R630, 2U
- Site: Anaheim (PFI colo)
- Detailed hardware / CPU / RAM / disk data comes from
sfsrv-ana'ssystem-details.txt(the OS can read all of this viadmidecode,lscpu, etc. — no need to duplicate here).
Why this dir exists separately from sfsrv-ana
- The iDRAC is a distinct management surface with its own credentials, protocol stack, and firmware lifecycle. Power events, BIOS updates, and console access live here.
- Inventory audits that track hardware (for hosting-agreement billing, depreciation, etc.) should see the physical box as its own entry independent of whatever OS happens to be running on it.
Refresh state
No ssh-target and no system-details.txt — iDRAC doesn't expose
a useful sshd for our inspect scripts. Host metadata comes from
sfsrv-ana's snapshot instead.
Discovered via
scripts/discover-fortigate.sh 10.250.250.1 on 2026-04-21 — iDRAC's
DHCP lease on the management interface (MAC 74:e6:e2:fe:2c:7c,
VCI iDRAC). Matched to sfsrv-ana via iDRAC Service Tag / physical
co-location on 2026-04-23.