Files
mesh-lab/scenarios/catalogue-media.yml
T
jschoubben 5d6e8fbe7a Rename mesh-control -> mesh-controller, substrate -> foundation
One name per thing, per the HQ glossary: the module/container/image/binary/repo
becomes mesh-controller, the seat the-controller, and the store+broker pair the
foundation (embedded base bundles, default template and example lock renamed with
their go:embed directives). No behaviour change — a pure vocabulary rename.

Claude-Session: https://claude.ai/code/session_01D6qtiYU3P9jk3pnAXyAFyx
2026-09-16 18:40:40 +02:00

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/foundation-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 foundation — 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-controller: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]