Files
vh 91bda3c480 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

103 lines
4.3 KiB
YAML

# meromero-charrp — G4-MeroMero-v2-31B NVFP4A16 char-rp PROSE seat (non-thinking, MULTIMODAL)
# on fv-ml1 GPU0. Replaces the retired Magidonia GGUF seat (char-rp-gguf / llama-charrp).
#
# Gemma-4 dense but with SLIDING-WINDOW attention -> KV-efficient, serves the full native 256K
# at ~2x concurrency. Vision enabled: preprocessor_config.json was materialized from
# processor_config.json's image_processor section (Gemma4ImageProcessor); audio is
# config-declared but weightless (no audio tensors) so it serves image + text.
#
# Co-located on GPU0 with vllm-aeon-gen (gen). util 0.52 leaves ~5GB GPU0 headroom
# (0.55 left only ~1.8GB). Tunables in .env.
name: meromero-charrp
services:
vllm-meromero-rp:
image: ${MEROMERO_IMAGE:-vllm/vllm-openai:latest}
container_name: ${MEROMERO_CONTAINER:-vllm-meromero-rp}
restart: unless-stopped
ipc: host
ports:
- "${MEROMERO_PORT:-8016}:8000"
volumes:
- /tank/aimodels:/tank/aimodels
environment:
- PYTORCH_CUDA_ALLOC_CONF=expandable_segments:True
- VLLM_API_KEY=${API_KEY:-}
command:
- ${MEROMERO_MODEL:-/tank/aimodels/meromero-v2-nvfp4-work/G4-MeroMero-v2-31B-NVFP4A16}
- --quantization
- compressed-tensors
- --served-model-name
- char-rp
- char-rp-thinking
# Tool-calling: Gemma-4 emits its OWN native syntax
# (<|tool_call>call:name{...}<tool_call|>), NOT the qwen3_coder XML the
# other seats use. vLLM 0.24 ships a matching `gemma4` parser whose token
# constants line up with this tokenizer's etc/eoc/escape tokens exactly.
# Without these two flags any tools-bearing request 400s outright.
- --tool-call-parser
- gemma4
- --enable-auto-tool-choice
# The gemma4 REASONING parser is what absorbs the <|channel>...<channel|>
# thought markers; without it they leak into `content` verbatim on the
# post-tool-response turn (upstream vllm #45834 — the chat template leaves
# the prompt inside an open channel block).
- --reasoning-parser
- gemma4
# Dwarf-panel CoT patch 2026-08-21: force-open <|channel> on enable_thinking:true
- --chat-template
- /tank/aimodels/meromero-v2-nvfp4-work/patched_chat_template.jinja
# MANDATORY companion to the reasoning parser on this seat. The parser
# reads enable_thinking from chat_template_kwargs and DEFAULTS IT TO TRUE
# (vllm/parser/gemma4.py:439). True makes is_reasoning_end() return False
# at a new turn, which pre-initialises the engine to REASONING -> ALL plain
# RP prose lands in reasoning_content with a NULL content, breaking every
# char-rp consumer. This template already defaults enable_thinking to false
# (chat_template.jinja:350), so passing it explicitly renders a BYTE-
# IDENTICAL prompt (verified across plain/tools/post-tool/system shapes) --
# it only corrects the parser's state machine. Do not remove.
- --default-chat-template-kwargs
- '{"enable_thinking": false}'
- --max-model-len
- "${MEROMERO_MAX_MODEL_LEN:-262144}"
- --max-num-seqs
- "${MEROMERO_MAX_NUM_SEQS:-32}"
- --gpu-memory-utilization
- "${MEROMERO_GPU_MEM_UTIL:-0.52}"
- --kv-cache-dtype
- fp8
- --trust-remote-code
deploy:
resources:
reservations:
devices:
- driver: nvidia
device_ids:
- "${MEROMERO_GPU_ID:-0}"
capabilities:
- gpu
healthcheck:
test: ["CMD", "curl", "-f", "http://localhost:8000/health"]
interval: 30s
timeout: 10s
retries: 3
start_period: 600s
networks:
- tnet
labels:
# STOPPED 2026-08-24 — superseded by stacks/gemma4-charrp (gemma-4-26B-A4B
# -it NVFP4 MoE) on the same port and the same served-model-names. Kept as
# the rollback seat: `docker compose up -d vllm-meromero-rp` here after
# stopping the gemma4 one, since both want :8016.
- homepage.group=AI - Dormant
- homepage.name=char-rp (MeroMero-v2 NVFP4) — rollback
- homepage.icon=mdi-drama-masks
- homepage.description=Superseded 2026-08-24 by the Gemma-4 26B-A4B MoE seat; dense 31B NVFP4A16, kept for rollback (fv-ml1 GPU0)
- homepage.href=http://10.251.50.54:${MEROMERO_PORT:-8016}/docs
networks:
tnet:
name: traefik-net
external: true