jschoubben
5d6e8fbe7a
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
35 lines
945 B
YAML
35 lines
945 B
YAML
# Three machines, joined one at a time.
|
|
#
|
|
# The point is not the third machine. It is that adding one changes **every other node's** peer
|
|
# list: each existing node has to be told again, or the newcomer is on a network nobody else can
|
|
# see. A mesh that only configures the arriving node looks like it worked and is half a network.
|
|
#
|
|
# So this scenario exists to be raised, then grown — enrol two, push, check; enrol the third,
|
|
# push, and check that the first two changed.
|
|
scenario: growing-mesh
|
|
|
|
segments:
|
|
hosting:
|
|
kind: public
|
|
cidr: [192.0.2.0/24]
|
|
|
|
machines:
|
|
anchor:
|
|
at: { segment: hosting, address: [192.0.2.10] }
|
|
egress: true
|
|
inbound: allow
|
|
laptop:
|
|
at: { segment: hosting, address: [192.0.2.20] }
|
|
egress: true
|
|
inbound: allow
|
|
workstation:
|
|
at: { segment: hosting, address: [192.0.2.30] }
|
|
egress: true
|
|
inbound: allow
|
|
|
|
images:
|
|
- mesh-controller:development
|
|
|
|
place:
|
|
all: [host, runtime]
|