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
41 lines
1.8 KiB
YAML
41 lines
1.8 KiB
YAML
# One machine that becomes a mesh and is then assigned gitlab — the exemplar of the tools-only,
|
|
# outbound-only external-SaaS integration (novox/hq ADR 0039). gitlab is the thinnest converted
|
|
# shape: NO service container, NO listener, NO provisioner — just a broker-bound runtime that serves
|
|
# the module's GitLab tools under a scoped account. Its sibling in kind is unifi (a tooled app), but
|
|
# gitlab has no server of its own to run alongside; it only ever calls out to a GitLab instance.
|
|
#
|
|
# The sharp point this bed proves is the Servarr lesson: the runtime MUST come up and serve its full
|
|
# tool surface even with NO valid GitLab credentials — the lab has no real GitLab, and gitlab's own
|
|
# token is a mesh-minted own-secret that points at nothing. gitlab's client is built lazily and never
|
|
# throws at registration, so the runtime logs `[mesh-tools] serving 23 tool(s)` and binds its serve
|
|
# queues regardless; a tool would only fail if it were actually invoked without real creds.
|
|
#
|
|
# MESH_LAB_HOST_BINARY=.../mesh-host MESH_LAB_BUNDLE=.../examples/substrate-first-node.lock
|
|
# scripts/build-module-runtime.sh gitlab builds mesh-runtime-gitlab:development into the local
|
|
# daemon, which the machine pulls from the internet over its uplink. gitlab needs no
|
|
# service image — it is tools-only.
|
|
scenario: tools-gitlab
|
|
|
|
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
|
|
# gitlab's runtime, built by scripts/build-module-runtime.sh gitlab into the local daemon and
|
|
# loaded onto the machine, which holds it by its own image ID. There is no
|
|
# service image: gitlab is tools-only and outbound-only.
|
|
- mesh-runtime-gitlab:development
|
|
|
|
place:
|
|
all: [host, runtime]
|