fv-ml1: finish the renumber the cutover missed -- 16 dead dashboard links

Every fv-ml1 link on the Homepage dashboard was broken. Measured against the
live dashboard API before the fix: 16 entries pointing at the dead 10.250.50.54
and zero at the live 10.251.50.54, covering gen, M.O.G.-SEC, Scriberr, Embed,
Rerank, Reward, Coder, Dockge and six dormant seats.

The miss was structural, not careless. fv-ml1-rename-sweep.sh works from an
allowlist assembled from files that mention the HOST, and a homepage.href label
mentions only an IP -- so every stack whose sole stale reference was a label
fell outside it. The allowlist now covers those 24 files, and records how to
derive the list next time (grep the old address, subtract history) rather than
enumerating from memory.

History is still untouched, and the exclusions are now written down with the
reason each one keeps the old address: recorded benchmark results, whose
base_url is part of a measurement's provenance; the one LiteLLM comment
preserving a retired hand-test endpoint; and the cutover runbooks, where the old
address is the subject matter.

Two bugs found while applying it, both fixed here:

  - deploy-stack.sh rejected any stack name containing a dot, so qwen3.5-122b,
    qwopus3.5-122b and mistral-medium-3.5 could not be deployed by the script at
    all. The check exists to stop path traversal, which means rejecting ".." and
    "/" -- not every dot. Traversal is now rejected explicitly and tested.
  - stacks/scriberr/.env.example allowed CORS only from the dead IP and from
    scriberr.ana.internal, which no longer resolves; the box is at the fv site
    and DNS already carries scriberr.fv.internal. The live .env had both stale
    origins, i.e. an allowlist with nothing reachable in it.

Host side, applied separately: canonical pushed for the 16 stacks whose only
difference from the host was this renumber, and an in-place address-only fix for
the nine whose host copy has genuinely drifted or has no canonical copy, so that
drift survives for a deliberate reconciliation instead of being clobbered. Every
compose.yaml on fv-ml1 now reads 10.251.50.54. The labels themselves only take
effect at container creation, so the running containers still need recreating.
This commit is contained in:
vh
2026-09-12 23:05:29 -07:00
parent f964a47262
commit 3132a16ca0
26 changed files with 163 additions and 106 deletions
+7 -7
View File
@@ -1,6 +1,6 @@
# char-rp-gguf
Dedicated GGUF **character-RP seat** on ana-ml2 GPU 0, served via llama.cpp
Dedicated GGUF **character-RP seat** on fv-ml1 GPU 0, served via llama.cpp
(`llama-server`) — **never Ollama**. Replaces the broken `ms32-24b-angel` NVFP4
serve (self-quant produced garbage even at greedy).
@@ -47,8 +47,8 @@ Canonical copies live here; authoritative copies live on the host under
`/opt/docker/compose/char-rp-gguf/`.
```bash
# On ana-ml2 (models already pre-pulled to /tank/aimodels/llm/rp/):
scripts/deploy-stack.sh ana-ml2 char-rp-gguf # from this workspace
# On fv-ml1 (models already pre-pulled to /tank/aimodels/llm/rp/):
scripts/deploy-stack.sh fv-ml1 char-rp-gguf # from this workspace
# or, on the host:
cd /opt/docker/compose/char-rp-gguf && cp .env.example .env && docker compose up -d
```
@@ -64,8 +64,8 @@ docker run -d --entrypoint python3 -v /tank:/tank vllm/vllm-openai:latest -c \
## Gateway wiring (ana-docker LiteLLM `:4000`)
`char-rp` → `http://10.250.50.54:8016/v1`, `char-rp-reasoning` →
`http://10.250.50.54:8018/v1`. Sampler defaults (per the model cards):
`char-rp` → `http://10.251.50.54:8016/v1`, `char-rp-reasoning` →
`http://10.251.50.54:8018/v1`. Sampler defaults (per the model cards):
- **char-rp (Magidonia / Mistral):** `temperature 1.0, top_p 0.95, min_p 0.03`;
no repetition penalty (Magistral is stable without one). Callers may override.
@@ -89,7 +89,7 @@ broken — do not re-serve it).
## Verify
```bash
curl -s http://10.250.50.54:8016/v1/models # char-rp up
curl -s http://10.250.50.54:8018/v1/models # char-rp-reasoning up
curl -s http://10.251.50.54:8016/v1/models # char-rp up
curl -s http://10.251.50.54:8018/v1/models # char-rp-reasoning up
nvidia-smi --query-gpu=index,memory.free --format=csv # GPU 0 margin
```
+5 -5
View File
@@ -1,4 +1,4 @@
# char-rp-gguf — dedicated GGUF character-RP seat on ana-ml2 GPU 0, REPLACING the
# char-rp-gguf — dedicated GGUF character-RP seat on fv-ml1 GPU 0, REPLACING the
# broken ms32-24b-angel NVFP4 serve (garbage output — bad self-quant W4A4).
#
# Two co-located llama.cpp (llama-server) instances on GPU 0, served alongside the
@@ -91,8 +91,8 @@ services:
- homepage.group=AI - Inference
- homepage.name=char-rp (Magidonia-24B GGUF)
- homepage.icon=mdi-drama-masks
- homepage.description=Dark-romantasy RP prose seat, non-thinking (llama.cpp, ana-ml2 GPU 0)
- homepage.href=http://10.250.50.54:${CHARRP_PORT:-8016}
- homepage.description=Dark-romantasy RP prose seat, non-thinking (llama.cpp, fv-ml1 GPU 0)
- homepage.href=http://10.251.50.54:${CHARRP_PORT:-8016}
# ── REASONING seat — NEO-CODE = Heretic2-Thinking (Qwen3.6-27B) managed thinking. gateway char-rp-reasoning. ──
llama-charrp-reasoning:
@@ -172,8 +172,8 @@ services:
- homepage.group=AI - Dormant
- homepage.name=char-rp-reasoning (QwQ-32B RpR-v4 GGUF)
- homepage.icon=mdi-brain
- homepage.description=Dark-romantasy RP reasoning seat, managed CoT (llama.cpp, ana-ml2 GPU 0)
- homepage.href=http://10.250.50.54:${CHARRP_REASONING_PORT:-8018}
- homepage.description=Dark-romantasy RP reasoning seat, managed CoT (llama.cpp, fv-ml1 GPU 0)
- homepage.href=http://10.251.50.54:${CHARRP_REASONING_PORT:-8018}
networks:
tnet: