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
27 lines
1.0 KiB
YAML
27 lines
1.0 KiB
YAML
# One machine running an object store that other machines use.
|
|
#
|
|
# The same shape as `a-provider`, against a different kind of provision, and that is the whole
|
|
# reason it exists: novox/hq 04-ISSUES and the work breakdown's Phase 1.1 ask whether a module can
|
|
# be given a bucket the way it is given a database. The provisioning model is name-agnostic — the
|
|
# control plane special-cases neither — so what is unproven is not the mesh's half but the last
|
|
# step, where something on the machine turns a delivered secret into a key that works.
|
|
#
|
|
# It also proves the half a database does not: **a consumer must not be able to reach another
|
|
# consumer's bucket.** One store holds everybody's, where one PostgreSQL server holds separate
|
|
# databases, so isolation here is a policy somebody wrote rather than a boundary the product has.
|
|
scenario: an-object-store
|
|
|
|
segments:
|
|
hosting:
|
|
kind: public
|
|
cidr: [192.0.2.0/24]
|
|
|
|
machines:
|
|
anchor:
|
|
at: { segment: hosting, address: [192.0.2.10] }
|
|
egress: true
|
|
inbound: allow
|
|
|
|
place:
|
|
all: [runtime]
|