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
30 lines
974 B
YAML
30 lines
974 B
YAML
# One machine that becomes a mesh and then assigns itself redis — a *provider* module.
|
|
#
|
|
# plex-node proves an assigned module that serves tools (novox/hq ADR 0052). This proves the same
|
|
# for a provider: redis's runtime runs its provisioner AND its tools as one process under one scoped
|
|
# broker account. The provisioner emitting a lifecycle event is the thing 0052 fixes — before it,
|
|
# the provisioner ran in a container with no broker and its emit could not fire.
|
|
scenario: redis-node
|
|
|
|
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
|
|
# Redis's tool+provisioner runtime, built by scripts/build-module-runtime.sh redis into the local
|
|
# daemon and loaded onto the machine, which holds it by its own image ID.
|
|
- mesh-runtime-redis:development
|
|
|
|
place:
|
|
all: [host, runtime]
|