Lumbridge Compute: telemetry and four-lane operations

2026-08-31 16:09:08 -07:00
commit ef9ec1dcd8
59 changed files with 11279 additions and 0 deletions
@@ -0,0 +1,35 @@
+apiVersion: lumbridge/v1
+kind: Scene
+metadata:
+  name: music
+  version: 2
+  description: "Music studio — MiniMax Music 3, with ears, voice, and the Lightning brain."
+  author: karti
+  tags: [music, creative, assistant]
+
+# v2, 2026-08-13: ACE-Step XL 4B is gone; MiniMax Music 3 takes the `music`
+# slot on :8010. Same port, same request fields, so :8010 callers are unchanged.
+#
+# brain-nemotron joins the scene, which is what forces `order: listed` below.
+# The old v1 used footprint-asc, and that is actively unsafe with a vLLM MoE in
+# the set: it would start the 38GB brain LAST, into a box already holding
+# ears+voice+music. The brain-nemotron entry is explicit that whatever holds
+# :8001 comes up first and alone, because its KV-profiling spike is not bounded
+# by gpu-memory-utilization. Declaring that footprint from an estimate once
+# already ran 11GB over and let the kernel OOM-kill `ears` on the next
+# transition. So: brain first, on the empty machine, then the small stuff.
+#
+# ears 5 + voice 8 + music ~24 + brain-nemotron 38 = ~75 GB of 121.
+# NOTE: the music figure is an ESTIMATE pending a boot-and-read-RSS measurement,
+# the same discipline brain-nemotron's comment demands. Do not trust it until
+# registry/models.yaml carries a measured number.
+models:
+  - brain-nemotron
+  - ears
+  - voice
+  - music
+
+budget_gb: 100
+activation:
+  order: listed
+  wait_healthy: true