WIP: catalogue-apps install bed (mongodb, unifi, marrytts)

Adds the mongodb runtime CLI (mongosh) to build-module-runtime.sh, a catalogue-apps scenario, and its install test. Proven so far: the ADR-0054 slug applies and the mesh accepts the push (mongodb consumer identity mesh_anchor_mongo fits). NOT green: the node applies but never reaches 'current' within 1200s — a persistent reconcile divergence (applied-but-never-current, no crash), likely a module declaring a resource its container mutates (issue-011 class). Needs live VM inspection to name the module. Not merged. Claude-Session: https://claude.ai/code/session_01LrgweAeERJYBg88c5cKDzF
2026-09-05 15:30:50 +02:00
parent a7afdbcd4f
commit 571a6cd6fd
3 changed files with 494 additions and 0 deletions
@@ -0,0 +1,53 @@
+# One machine that becomes a mesh and is then assigned a SECOND wave of modules at once — the ones
+# converted this session (novox/hq ADR 0039/0048/0052): mongodb, unifi and marrytts, with postgres
+# carried along as a known-good control. This is catalogue-small's sibling: same first-node substrate,
+# same one-push co-residence, a different (and heavier) set of modules.
+#
+# The four exercise the three converted shapes:
+#   - mongodb — a database PROVIDER shaped like postgres (server + a broker-bound runtime carrying
+#     `mongosh`, the runtime running the provisioner over the ADR-0048 MESH_RECEIVES contract).
+#   - unifi   — a tooled APP (server + a broker-bound runtime that serves tools; no provisioner),
+#     shaped like plex.
+#   - marrytts — a manifest-only PLAIN container: no runtime, no tools, it only has to come up.
+#   - postgres — the known-good provider control, verbatim from catalogue-small.
+#
+# None of the four share a directory, so the shared-workspace refusal (novox/hq 04-ISSUES/012) does
+# not bite; that class stays for a later bed.
+#
+#   MESH_LAB_HOST_BINARY=.../mesh-host   MESH_LAB_BUNDLE=.../examples/substrate-first-node.lock
+#   scripts/build-module-runtime.sh {mongodb,unifi,postgres} build the runtime images into the local
+#   daemon (mongodb carries mongosh; unifi and postgres carry their CLIs). The service images
+#   (mongo, unifi-controller, marytts, postgres) must be in the local daemon to be stocked.
+scenario: catalogue-apps
+
+segments:
+  hosting:
+    kind: public
+    cidr: [192.0.2.0/24]
+
+machines:
+  anchor:
+    at: { segment: hosting, address: [192.0.2.10] }
+    inbound: allow
+    # Sized up past catalogue-small's 6GiB: this wave carries two heavy JVM/embedded-DB service
+    # containers (the UniFi controller and MaryTTS) on top of the substrate, mongodb, postgres and
+    # three node runtimes — a dozen containers, two of them memory-hungry at startup.
+    memory: 8GiB
+    cpus: 4
+
+images:
+  # The first-node substrate: store, broker, control.
+  - postgres:17-alpine
+  - cloudamqp/lavinmq:latest
+  - mesh-control:development
+  # The module server images.
+  - mongo:7
+  - lscr.io/linuxserver/unifi-controller:latest
+  - synesthesiam/marytts:lab
+  # The runtimes built by scripts/build-module-runtime.sh and stocked here. marrytts needs none.
+  - mesh-runtime-mongodb:development
+  - mesh-runtime-unifi:development
+  - mesh-runtime-postgres:development
+
+place:
+  all: [host, runtime]