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
30 lines
911 B
YAML
30 lines
911 B
YAML
# One machine that becomes a mesh and then assigns itself the audit logger.
|
|
#
|
|
# The foundation is first-node's — a store, a broker, the control plane — and one module image on
|
|
# top: the tool runtime carrying the audit-logger (mesh-catalog). The node enrols itself and the
|
|
# mesh assigns it the audit logger, so its events account is one the mesh delivered, not the
|
|
# broker's own (novox/hq ADR 0048).
|
|
scenario: audit-node
|
|
|
|
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-controller:development
|
|
# The tool runtime with the audit-logger, built by scripts/build-runtime-image.sh into the local
|
|
# daemon and loaded onto the machine, which holds it by its own image ID.
|
|
- mesh-runtime-audit:development
|
|
|
|
place:
|
|
all: [host, runtime]
|