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
parent fde7834635
commit 91bda3c480
31 changed files with 115 additions and 112 deletions
@@ -0,0 +1,44 @@
+# ana-ml2 pool-health actions (operator-approved 2026-09-09, "all 3 on clean context").
+#
+#   1. kick a scrub of `tank` (2 CKSUM on nvme7n1 after the 09-05 boot resilver,
+#      no scrub since 04-12) — polled separately; `zpool clear` only after a
+#      clean pass, by hand, never in this playbook.
+#   2. install nvme-cli so nvme7's SMART counters can be read.
+#   3. reclaim zroot (91%): dangling images + build cache ONLY. Never `prune -a`
+#      here — tagged idle images include rollback seats.
+#
+# Rerunnable: a second run shows the scrub step skipped (in progress / done
+# within the hour is not detected — the guard is "not already scrubbing"),
+# nvme-cli ok, prunes ok with 0 B reclaimed.
+
+steps:
+  - name: Start scrub of tank (skip if one is already running)
+    shell: zpool scrub tank
+    sudo: true
+    when: "! zpool status tank | grep -q 'scrub in progress'"
+
+  - name: Install nvme-cli
+    shell: DEBIAN_FRONTEND=noninteractive apt-get install -y -q nvme-cli
+    sudo: true
+    creates: /usr/sbin/nvme
+
+  - name: Prune dangling docker images (NOT -a)
+    shell: docker image prune -f | tail -1
+    sudo: true
+
+  - name: Prune docker build cache
+    shell: docker builder prune -f | tail -1
+    sudo: true
+
+verify:
+  - name: Scrub is in progress or already completed today
+    shell: "zpool status tank | grep -Eq 'scrub in progress|scrub repaired .* on .*$(date +%b\\ *%e)'"
+    changed_when: "false"
+
+  - name: nvme binary present
+    shell: test -x /usr/sbin/nvme
+    changed_when: "false"
+
+  - name: zroot usage after prune
+    shell: df -h / | tail -1
+    changed_when: "false"