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
48 lines
2.2 KiB
YAML
48 lines
2.2 KiB
YAML
# 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] }
|
|
egress: true
|
|
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:
|
|
- mesh-control:development
|
|
# 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]
|