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
30 lines
977 B
YAML
30 lines
977 B
YAML
# One machine that becomes a mesh and then assigns itself redis — a *provider* module.
|
|
#
|
|
# plex-node proves an assigned module that serves tools (novox/hq ADR 0052). This proves the same
|
|
# for a provider: redis's runtime runs its provisioner AND its tools as one process under one scoped
|
|
# broker account. The provisioner emitting a lifecycle event is the thing 0052 fixes — before it,
|
|
# the provisioner ran in a container with no broker and its emit could not fire.
|
|
scenario: redis-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
|
|
# Redis's tool+provisioner runtime, built by scripts/build-module-runtime.sh redis into the local
|
|
# daemon and loaded onto the machine, which holds it by its own image ID.
|
|
- mesh-runtime-redis:development
|
|
|
|
place:
|
|
all: [host, runtime]
|