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
49 lines
2.3 KiB
YAML
49 lines
2.3 KiB
YAML
# One machine that becomes a mesh and is then assigned TWO media modules at once — sonarr and radarr —
|
|
# which both ACCESS the same operator-owned directory. This is the bed that proves novox/hq ADR 0051
|
|
# (04-ISSUES/036, 012): a module accesses shared operator data, it does not own it, so two modules
|
|
# naming the same path co-resolve where before they collided.
|
|
#
|
|
# The pair is the tightest co-access case:
|
|
# - sonarr accesses /services/media/downloads (shared) and /services/media/series (its own use).
|
|
# - radarr accesses /services/media/downloads (shared) and /services/media/movies (its own use).
|
|
# /services/media/downloads is the exact duplicate path the resolver refused pre-0051 (two modules
|
|
# "both declare the path"). Now each declares it as an ACCESS, not a `directory` resource — an access
|
|
# never enters the owner map — so the two co-resolve and one push configures both.
|
|
#
|
|
# The host refuses an access whose path is absent at apply (novox/hq ADR 0051): shared data is the
|
|
# operator's, mounted and never created by the mesh. So the operator provides
|
|
# /services/media/{downloads,series,movies} on the anchor BEFORE the modules apply; the test does this
|
|
# after enrol and before the push. Each module additionally OWNS its own config directory
|
|
# (/services/{sonarr,radarr}/config), which the mesh does create.
|
|
#
|
|
# MESH_LAB_HOST_BINARY=.../mesh-host MESH_LAB_BUNDLE=.../examples/substrate-first-node.lock
|
|
# scripts/build-module-runtime.sh {sonarr,radarr} build the two runtime images into the local daemon
|
|
# (they speak HTTP and need no CLI added). The service images lscr.io/linuxserver/{sonarr,radarr}
|
|
# must be in the local daemon to be stocked.
|
|
scenario: catalogue-media
|
|
|
|
segments:
|
|
hosting:
|
|
kind: public
|
|
cidr: [192.0.2.0/24]
|
|
|
|
machines:
|
|
anchor:
|
|
at: { segment: hosting, address: [192.0.2.10] }
|
|
egress: true
|
|
inbound: allow
|
|
# Two *arr apps (server + runtime each) on top of the first-node substrate — seven containers.
|
|
# The Servarr images are lighter than catalogue-apps' JVM pair, so catalogue-small's 6GiB is
|
|
# ample headroom.
|
|
memory: 6GiB
|
|
cpus: 4
|
|
|
|
images:
|
|
- mesh-control:development
|
|
# The two runtimes built by scripts/build-module-runtime.sh and stocked here.
|
|
- mesh-runtime-sonarr:development
|
|
- mesh-runtime-radarr:development
|
|
|
|
place:
|
|
all: [host, runtime]
|