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-ana-container
SureFire-client container workload running on sfsrv-ana (SureFire's
Proxmox at 10.250.250.115). PFI-managed under the hosting
agreement.
Client context
- Client: SureFire
- PFI role: full-service managed host
Network
- LAN IP: 10.250.150.100
- FQDN: not in DNS yet — add to workstation
/etc/hosts:10.250.150.100 sf-ana-container - SSH:
vhoang@10.250.150.100(confirmed)
Infrastructure
- Hypervisor:
sfsrv-ana(SureFire Proxmox, 10.250.250.115) - Site: Anaheim (PFI colo)
- Subnet:
10.250.150.0/24— dedicated SF container subnet
Role
Container/VM workload for SureFire. Specific services TBD — refresh the server-info snapshot once SSH is verified:
scripts/refresh-server-info.sh sf-ana-container
Backup coverage
- VM-image via sfsrv-ana vzdump: status unknown — depends on what
backup jobs are configured on that Proxmox. Audit via
scripts/refresh-proxmox-info.sh sfsrv-ana. - File-level restic: not yet configured — worth adding once we know what state the container runs (DBs, configs, app data).
Discovered via
scripts/discover-fortigate.sh 10.250.250.1 on 2026-04-21 (MAC
6a:09:9a:8a:08:a5).