# One machine that becomes a mesh and then assigns itself redis — a *provider* module.
#
# A bed proving an assigned module that serves tools (novox/hq ADR 0052) once lived beside this; 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
  # The vault's, for the beds that install the catalogue's redis: its own password is a secret the
  # vault provides (novox/hq ADR 0085).
  - mesh-runtime-mesh-vault:development

place:
  all: [host, runtime]