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.

playbooks/fv-ml1-overcommit-memory.yaml

@@ -0,0 +1,43 @@
+# Make vm.overcommit_memory=1 durable on ana-ml2 (GPU inference host).
+#
+# Why: ana-ml2 runs vm.overcommit_memory=0 (heuristic) with zero swap, so the
+# CommitLimit is ~RAM/2 (~283 GB of 566 GB). The resident vLLM services already
+# commit ~224 GB of address space, leaving < 60 GB of headroom. A large model-file
+# mmap (e.g. the 50 GB NVFP4 shard during HF->native conversion, or a vLLM model
+# load) then fails with ENOMEM despite ~393 GB of RAM actually being free — the
+# kernel rejects the *commit*, not the allocation.
+#
+# overcommit_memory=1 (always overcommit) is the conventional setting for ML hosts
+# that mmap large files: the real RAM is there to back the pages, and the heuristic
+# accounting is the only thing in the way. Operator-directed permanent + durable
+# (2026-06-17). A drop-in under /etc/sysctl.d/ applies at every boot.
+#
+# Run:  scripts/elway infra-ops@ana-ml2 --playbook playbooks/ana-ml2-overcommit-memory.yaml
+# Rerunnable: a second run shows the write step `skipped` (idempotent via when:).
+
+vars:
+  dropin: /etc/sysctl.d/99-overcommit-memory.conf
+  setting: "vm.overcommit_memory = 1"
+
+steps:
+  - name: Write durable overcommit sysctl drop-in
+    # elway runs steps as the SSH user, so a shell `>` redirect can't write a
+    # root-owned path — pipe through `sudo tee` (infra-ops has NOPASSWD sudo).
+    shell: |
+      printf '# GPU inference host: large model-file mmaps (NVFP4 native convert, vLLM loads)\n# exceed the heuristic CommitLimit (overcommit=0 + zero swap) despite ample free RAM.\n# Operator-directed permanent setting 2026-06-17.\n%s\n' '{{ setting }}' | sudo tee {{ dropin }} >/dev/null
+    # Skip the write if the drop-in already holds exactly this line.
+    when: "! grep -qxF '{{ setting }}' {{ dropin }} 2>/dev/null"
+
+  - name: Apply all sysctl drop-ins now
+    shell: sudo sysctl --system >/dev/null
+    # Applying is a no-op when the runtime value already matches.
+    changed_when: "false"
+
+verify:
+  - name: Runtime vm.overcommit_memory is 1
+    shell: test "$(cat /proc/sys/vm/overcommit_memory)" = "1"
+    changed_when: "false"
+
+  - name: Drop-in file persists the setting (survives reboot)
+    shell: grep -qxF '{{ setting }}' {{ dropin }}
+    changed_when: "false"