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.
This commit is contained in:
@@ -2,7 +2,7 @@
|
||||
|
||||
Priority 2 completed 2026-09-11: pfi-postgres, esh-vm-db, pbs-ana and pbs-nh3
|
||||
added with 16 alerts. Live samples verified, including both PBS datastores.
|
||||
Fleet 17/18 up (known ana-ml2 outage). See `configs/beszel-agent/PRIORITY2.md`.
|
||||
Fleet 17/18 up (known fv-ml1 outage). See `configs/beszel-agent/PRIORITY2.md`.
|
||||
|
||||
Hub: http://10.250.50.70:8090 (ana-docker), version 0.18.7 at the
|
||||
2026-09-10 wiring. The hub also retains corviduo-dev's existing registration.
|
||||
@@ -12,12 +12,12 @@ esh-pve and esh-pve-nas); 13 systems total and 20 additional alert rules.
|
||||
See `configs/beszel-agent/README.md`. Subsequently nh3-nas was installed via
|
||||
DSM Docker and registered with four alerts (14 registrations total). Recovery
|
||||
verification at 2026-09-12 01:51Z: all six priority-1 hosts up, Synology live
|
||||
filesystem samples verified; fleet 13/14 up with known ana-ml2 outage.
|
||||
filesystem samples verified; fleet 13/14 up with known fv-ml1 outage.
|
||||
|
||||
| Host | Compose directory under `/opt/docker/compose/` | Additional filesystems |
|
||||
|---|---|---|
|
||||
| ana-docker | beszel | /mnt/backup |
|
||||
| ana-ml2 | beszel-agent-ana | /tank, /home |
|
||||
| fv-ml1 | beszel-agent-ana | /tank, /home |
|
||||
| nh3-docker | beszel-agent-nh3 | none |
|
||||
| esh-docker-vm (hub name esh-vm-docker) | beszel-agent-esh | /mnt/backup, /mnt/books |
|
||||
| irv-ml1 | beszel-agent-irv | /worktank, /storetank, /mnt/smithy |
|
||||
@@ -37,14 +37,14 @@ and `DEPLOY_SUDO=1` for root-owned directories. Example:
|
||||
|
||||
```sh
|
||||
DEPLOY_SUDO=1 DEPLOY_DEST_STACK=beszel-agent-ana \
|
||||
scripts/deploy-stack.sh infra-ops@10.250.50.54 beszel --compose
|
||||
scripts/deploy-stack.sh infra-ops@10.251.50.54 beszel --compose
|
||||
```
|
||||
|
||||
Agents use host-specific overrides selected by live `.env`:
|
||||
|
||||
```dotenv
|
||||
COMPOSE_PROFILES=agent
|
||||
COMPOSE_FILE=compose.yaml:hosts/ana-ml2.yaml
|
||||
COMPOSE_FILE=compose.yaml:hosts/fv-ml1.yaml
|
||||
BESZEL_EXTRA_FS=/extra-filesystems/tank,/extra-filesystems/home
|
||||
```
|
||||
|
||||
@@ -71,7 +71,7 @@ hub public key. Never copy live tokens into version control.
|
||||
|
||||
## GPU telemetry
|
||||
|
||||
ana-ml2 and irv-ml1 use `henrygd/beszel-agent-nvidia:0.18.7` with NVIDIA
|
||||
fv-ml1 and irv-ml1 use `henrygd/beszel-agent-nvidia:0.18.7` with NVIDIA
|
||||
`utility` access to all GPUs. Both hosts already have NVIDIA Container Toolkit.
|
||||
This collects per-card utilization, VRAM, temperature, and power draw without
|
||||
changing the serving containers or GPU power limits. Verified hub samples
|
||||
@@ -111,7 +111,7 @@ Thirty rules cover the seven hosts above under the existing operator user:
|
||||
| CPU | >95% | 15 minutes |
|
||||
| Memory | >90% | 10 minutes |
|
||||
| Offline | down | 2 minutes |
|
||||
| Temperature (ana-ml2 and irv-ml1) | >85 C | 5 minutes |
|
||||
| Temperature (fv-ml1 and irv-ml1) | >85 C | 5 minutes |
|
||||
|
||||
CPU thresholds are sustained-load warnings; expected long-running compute may
|
||||
need tuning. GPU utilization alone is not an alarm because busy GPUs are normal.
|
||||
@@ -125,7 +125,7 @@ The bridge at `services/beszel-althing/` forwards through `postbox` to the
|
||||
was replaced with this verified route. Miranda is a later cutover, not enabled.
|
||||
See that service's README for operation and recipient changes.
|
||||
|
||||
Acceptance on 2026-09-10: ana-ml2 Disk was temporarily lowered to 1%/1 minute;
|
||||
Acceptance on 2026-09-10: fv-ml1 Disk was temporarily lowered to 1%/1 minute;
|
||||
the real alert reached althing at 15:29:45Z, thread
|
||||
`01M25Z0WFDJM92GPTJQF769HJ7`. The threshold was then restored to 85%/5 minutes.
|
||||
Verification uses `postbox thread`, which does not consume the inbox.
|
||||
|
||||
Reference in New Issue
Block a user