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
53 lines
2.4 KiB
YAML
53 lines
2.4 KiB
YAML
# The usage context store, proved end to end (novox/hq ADR 0054). A postgres PROVIDER and the
|
|
# model-usage CONSUMER ride one node; the substrate (store, broker, control) owns the other. As in
|
|
# two-node-db, the app-postgres provider and the mesh's own substrate store both want host port 5432,
|
|
# so they cannot share a machine — the substrate lives on `anchor` and NOTHING else, and `laptop`
|
|
# runs postgres plus model-usage. Provider and consumer are co-located on laptop, so only enrolment
|
|
# crosses to anchor, over the underlay both machines already share.
|
|
#
|
|
# The property the bed proves: a usage event emitted into the mesh is upserted into model-usage's
|
|
# provisioned postgres store, at BOTH grains (licence and session, differing only in `consumer`),
|
|
# LATEST-per-key, and IN THE CLEAR — an ordinary select returns the numeric value and its raw payload.
|
|
#
|
|
# MESH_LAB_HOST_BINARY=.../mesh-host MESH_LAB_BUNDLE=.../examples/substrate-first-node.lock
|
|
# Build BOTH runtime images into the local daemon first (the scenario stocks and serves them by
|
|
# digest, which is where the host pulls them from):
|
|
# scripts/build-module-runtime.sh postgres /tmp/postgres.tar
|
|
# scripts/build-module-runtime.sh model-usage /tmp/model-usage.tar
|
|
scenario: model-usage-bed
|
|
|
|
segments:
|
|
hosting:
|
|
kind: public
|
|
cidr: [192.0.2.0/24]
|
|
|
|
machines:
|
|
# The substrate ONLY: store, broker, control — three containers.
|
|
anchor:
|
|
at: { segment: hosting, address: [192.0.2.10] }
|
|
egress: true
|
|
inbound: allow
|
|
memory: 4GiB
|
|
cpus: 4
|
|
# The postgres PROVIDER (server + broker-bound runtime) and the model-usage CONSUMER (its run-once
|
|
# migrate and its long-lived event runtime). The 5432-vs-substrate conflict is gone because the
|
|
# substrate store is on the OTHER node. The runtime images plus postgres:17-alpine are pulled from
|
|
# the internet over the uplink; forty gigabytes holds them with room to spare.
|
|
laptop:
|
|
at: { segment: hosting, address: [192.0.2.20] }
|
|
egress: true
|
|
inbound: allow
|
|
memory: 4GiB
|
|
cpus: 4
|
|
disk: 40GiB
|
|
|
|
images:
|
|
- mesh-control:development
|
|
# The per-module runtimes, built by scripts/build-module-runtime.sh and stocked here. Each carries
|
|
# its module's code — postgres its provisioner, model-usage its consumer, tools and run-once migrate.
|
|
- mesh-runtime-postgres:development
|
|
- mesh-runtime-model-usage:development
|
|
|
|
place:
|
|
all: [host, runtime]
|