jschoubben
a740959cb0
Five steps now instead of three. A sealed machine goes from bare to a container runtime, a store, the inventory database, that database's schema applied by mesh-control, and LavinMQ running and answering. The database is called inventory rather than mesh. ADR 0008 grants a context only what it exclusively owns and ADR 0006 says the mesh database names a thing that will not exist -- so one database per context, and there is one context. The broker is in the bundle because ADR 0006 now says it must be: the control plane reaches a node only over the link, the link is the broker, so nothing can provision the broker. Two images, which is the cost that record accepts. Verified by reading the system rather than the report: inventory present and mesh absent, the node table with its indexes, the migration row, lavinmqctl answering, 5672 listening. Sealed confirmed both ways -- the internet times out, the lab registry returns 200. Then rebooted, which was the part worth doing rather than assuming. Everything returned: docker from boot: enabled, both containers because this host creates every container --restart unless-stopped, the schema intact in its volume. Three reconciles before and one after all report no change. One thing that reads as a success and was not: the first sealed check said the machine could reach example.com. It was the test that was wrong -- a helper script pasted arguments into a shell line, so a command with quotes was re-split and ran on the workstation. The machine had been sealed the whole time. The helper now requotes each argument.
49 lines
2.1 KiB
Markdown
49 lines
2.1 KiB
Markdown
# Examples
|
|
|
|
## `substrate-first-node.lock`
|
|
|
|
What a machine must be before a mesh exists — steps 0 to 4 of the bootstrap in
|
|
[novox/hq `07-the-substrate.md`](https://git.novox.be/novox/hq):
|
|
|
|
```
|
|
0 a container runtime
|
|
1 the store runs
|
|
2 a database per context one today, `inventory`
|
|
3 that context's schema mesh-control migrate
|
|
4 the broker runs
|
|
```
|
|
|
|
**It stops there, and the file says why.** Step 5 is a virtual host, a credential and a
|
|
certificate; step 6 is the control plane running. Nothing consumes any of them yet, and a bundle
|
|
whose last step cannot be checked is worse than a shorter one.
|
|
|
|
Build a host carrying it:
|
|
|
|
```
|
|
make host SYSTEM=arch BUNDLE=examples/substrate-first-node.lock
|
|
```
|
|
|
|
**The registry address and digests have to be replaced before this is useful.** They are written
|
|
as `192.0.2.250:5000/…@sha256:…` because a digest belongs to whatever registry serves it — here,
|
|
one a lab scenario raises, which reports its digests when it comes up. That is not a placeholder
|
|
to be tidied away: a bundle is built *for a target*, and which registry that target pulls from is
|
|
part of the target.
|
|
|
|
### What was verified, and how
|
|
|
|
On a lab machine confirmed sealed — `curl https://example.com` times out, the lab registry answers
|
|
200 — the whole bundle applied from bare: eight resources, `inventory` created and `mesh` nowhere,
|
|
the `node` table present with its indexes, the migration recorded, and LavinMQ answering
|
|
`lavinmqctl status` with AMQP listening on 5672.
|
|
|
|
Three consecutive reconciles after that: **already matches — 8 resource(s) checked**, each time.
|
|
|
|
Then the machine was **rebooted**, and everything came back: docker from `boot: enabled`, both
|
|
containers because the host creates every container `--restart unless-stopped`
|
|
(`internal/apply/apply.go`), the schema intact in its named volume, and reconcile still finding
|
|
nothing to do.
|
|
|
|
The reboot is worth doing rather than assuming. Nothing in the declaration asks for a container to
|
|
return, so that it does is a property of the host, and the only way to know it holds is to take
|
|
the machine away and give it back.
|