Files

T

vh 3132a16ca0 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.

2026-09-12 23:05:29 -07:00

4.3 KiB

Raw Blame History

char-rp-gguf

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).

Two co-located instances, alongside the 35B-A3B heretic gen (qwen36-27b-aeon, :8015):

service	port	gateway alias	model	role
`llama-charrp`	8016	`char-rp`	TheDrummer Magidonia-24B-v4.3 Q6_K	non-thinking prose seat
`llama-charrp-reasoning`	8018	`char-rp-reasoning`	ArliAI QwQ-32B-RpR-v4 Q5_K_M	managed-reasoning seat

Why these two models

Requirements (operator, 2026-07-08): highest prose quality; ≥50 tok/s (single-seat); very low refusal for dark explicit romantasy; dense; GGUF-via-llama.cpp; thinking strongly preferred; must fit alongside the 35B-A3B on GPU 0.

Magidonia-24B-v4.3 (char-rp) — Magistral (Mistral) dark-romantasy RP tune. Live-tested: elite literary prose, zero refusal on explicit scenes, precise POV/instruction adherence, ~65 tok/s at Q6_K. The prose star.
QwQ-32B-RpR-v4 (char-rp-reasoning) — QwQ reasoning RP tune whose reasoning data was generated with QwQ-abliterated, so it does not re-censor inside the think phase — the failure mode that disqualified Pantheon-Reasoning-27B (its DeepSeek-distilled traces reason themselves into refusals). llama.cpp manages QwQ reasoning: --reasoning on surfaces the trace in reasoning_content (content stays clean prose, no <think> leak) and --reasoning-budget caps the CoT. ~50 tok/s at Q5_K_M (46 at Q6).

Why not one model for both: no single dense 24–32B is both an elite non-thinking prose seat and a clean managed-reasoning seat on llama.cpp. Magidonia's Magistral [THINK] discipline is loose (won't reliably close [/THINK] on substantive reasoning → prose bleeds into reasoning_content, content empties). Cydonia-R1's <think> is emergent, so llama.cpp can't manage/cap it → runaway CoT that never reaches the prose. QwQ's template opens <think> natively → llama.cpp manages+caps it. Best-of-breed per seat. See the compose header for the one-model fallback.

Alternate prose model: MS3.2-PaintedFantasy-v4.1-24B (Magistral; more literary flair, looser POV adherence) — swap via CHARRP_MODEL in .env. All candidate GGUFs are pre-pulled to /tank/aimodels/llm/rp/.

Deploy

Canonical copies live here; authoritative copies live on the host under /opt/docker/compose/char-rp-gguf/.

# 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

GGUFs are pulled with a detached huggingface_hub container, e.g.:

docker run -d --entrypoint python3 -v /tank:/tank vllm/vllm-openai:latest -c \
  'from huggingface_hub import hf_hub_download as d; \
   d(repo_id="bartowski/TheDrummer_Magidonia-24B-v4.3-GGUF", \
     filename="TheDrummer_Magidonia-24B-v4.3-Q6_K.gguf", local_dir="/tank/aimodels/llm/rp")'

Gateway wiring (ana-docker LiteLLM `:4000`)

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.
char-rp-reasoning (QwQ RpR-v4): temperature 1.0, top_k 40, min_p 0.02; no repetition / DRY / XTC penalties (RpR card is explicit about this). Reasoning surfaces in reasoning_content.

Do not carry the Qwen-specific chat_template_kwargs.enable_thinking on these aliases — it is meaningless to Mistral/QwQ templates. Reasoning is controlled server-side (--reasoning on on :8018).

Revert

docker compose -f /opt/docker/compose/char-rp-gguf/compose.yaml down

The retired ms32-24b-angel stack is left staged for reference (its NVFP4 quant is broken — do not re-serve it).

Verify

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

4.3 KiB Raw Blame History Unescape Escape