catalogue-mqtt: prove the run-once primitive end to end

A bed that assigns mosquitto and asserts the run-once step seeded dynsec before the broker: the bootstrap ran to completion (not left running), the seed is on disk owned by the broker's uid, the broker is up and stable (it crash-loops against an unseeded store, so a stable broker is the proof), and the node reached current. On top, the seeded admin authenticates over MQTT and the provisioner grants a scoped client a consumer connects with. build-module-runtime.sh gains a mosquitto arm (install mosquitto_ctrl from the mosquitto package — it is not in mosquitto-clients on bookworm, and a musl binary from eclipse-mosquitto would not load) and compiles the module's bootstrap/index.ts entrypoint. Claude-Session: https://claude.ai/code/session_01LrgweAeERJYBg88c5cKDzF
2026-09-06 00:33:41 +02:00
parent 8558ffdc8e
commit 62e479b9fe
3 changed files with 420 additions and 1 deletions
@@ -0,0 +1,46 @@
+# One machine that becomes a mesh and then assigns itself mosquitto — the bed that proves the
+# run-once primitive (novox/hq ADR 0052) end to end.
+#
+# mosquitto is the sharp case ADR 0052 was written for: its Dynamic Security plugin loads at broker
+# start and refuses to come up unless `dynamic-security.json` already holds an admin client. That
+# file is not state a reconcile loop can carry — it is a step that must run once, after the data
+# directory exists and BEFORE the broker container starts. mosquitto's manifest declares that step
+# as a `run-once: true` init container, placed before the `server` (broker) container: the same
+# runtime image, carrying mosquitto's own `bootstrap/` entrypoint and `mosquitto_ctrl`, run to
+# completion under the module's own account. The host runs it, requires exit 0, and only then reaches
+# the broker — so "the broker came up" is itself the proof the seed ran, because an unseeded store
+# crash-loops the broker.
+#
+#   MESH_LAB_HOST_BINARY=.../mesh-host   MESH_LAB_BUNDLE=.../examples/substrate-first-node.lock
+#   scripts/build-module-runtime.sh mosquitto builds mesh-runtime-mosquitto:development (carrying
+#   mosquitto_ctrl and the compiled bootstrap entrypoint) into the local daemon, which this scenario
+#   stocks and serves by digest from its own registry. eclipse-mosquitto:2 must be in the local
+#   daemon to be stocked.
+scenario: catalogue-mqtt
+
+segments:
+  hosting:
+    kind: public
+    cidr: [192.0.2.0/24]
+
+machines:
+  anchor:
+    at: { segment: hosting, address: [192.0.2.10] }
+    inbound: allow
+    memory: 3GiB
+    cpus: 2
+
+images:
+  # The first-node substrate: store, broker, control.
+  - postgres:17-alpine
+  - cloudamqp/lavinmq:latest
+  - mesh-control:development
+  # mosquitto's broker (the service image) and its runtime, the latter built by
+  # scripts/build-module-runtime.sh mosquitto into the local daemon and stocked into the scenario's
+  # own registry, which is where the host pulls it from. The runtime image is reused for the
+  # run-once bootstrap step and for the serve container.
+  - eclipse-mosquitto:2
+  - mesh-runtime-mosquitto:development
+
+place:
+  all: [host, runtime]