# The control plane's store restarting while a machine joins (novox/hq issue 083).
#
# Adopting the foundation's store — the first thing a control-node does, and the first thing a
# migration does — recreates it, and for those seconds the control plane cannot write. A machine
# enrolling then used to be refused, or worse, left with its token spent and no identity. This
# raises the foundation on `anchor`, takes its store away, has `laptop` enrol into the gap and
# brings the store back: the enrolment must complete on its own.
scenario: store-window

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
  laptop:
    at: { segment: hosting, address: [192.0.2.20] }
    egress: true
    inbound: allow
    memory: 1GiB

images:
  - mesh-controller:development

place:
  all: [host, runtime]