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
31 lines
1.0 KiB
YAML
31 lines
1.0 KiB
YAML
# One machine that becomes a mesh and grants a consumer an S3 bucket from an assigned minio provider.
|
|
#
|
|
# The postgres bed proves the provider/consumer contract for a database; this proves it for object
|
|
# storage (novox/hq ADR 0052/0053), on a provider whose code drives the `mc` CLI (so the runtime image
|
|
# carries it): minio is assigned, a consumer that requires s3-bucket is assigned, and the mesh mints
|
|
# one secret key; minio's provisioner creates a bucket and a service account under the access key the
|
|
# mesh derived with the secret it minted, and the consumer reaches its bucket with only that.
|
|
scenario: minio-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
|
|
# minio's runtime, built by scripts/build-module-runtime.sh minio (it carries mc), loaded onto
|
|
# the machine.
|
|
- mesh-runtime-minio:development
|
|
|
|
place:
|
|
all: [host, runtime]
|