jschoubben
5c91c0ecd2
Every scenario that places a container runtime gives each of its machines `egress: true` — a node that runs modules pulls images from the internet, which is what a node does. The underlay-only scenarios (bootstrap-single, behind-nat, segmented-and-unforwardable, the-ordinary-shape, two-on-a-segment) stay sealed on purpose: an extra NIC would change the very reachability they are asserting about. `images:` keeps only the mesh's own — 55 third-party entries leave whole-mesh-full alone, and the machine fetches them itself by the digest its module.json already pins. The whole-mesh beds also say per machine which of ours they get: novox the substrate control plane and its own fifteen runtimes, ace its twenty-four, the two workstations one each. That is not a lab economy. An operator's workstation holds the images its own modules need, and giving these two the union would put some thirty gigabytes onto a thirty-gigabyte disk. bootstrap-with-registry.yml is deleted. It existed only to demonstrate the lab's registry, nothing referenced it, and there is nothing left for it to demonstrate. Claude-Session: https://claude.ai/code/session_01LrgweAeERJYBg88c5cKDzF
40 lines
1.7 KiB
YAML
40 lines
1.7 KiB
YAML
# 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
|
|
# pulls from the internet over its uplink. 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] }
|
|
egress: true
|
|
inbound: allow
|
|
memory: 3GiB
|
|
cpus: 2
|
|
|
|
images:
|
|
- mesh-control:development
|
|
- mesh-runtime-mosquitto:development
|
|
|
|
place:
|
|
all: [host, runtime]
|