place: the host — the lab acquires a consumer · 16c13807a9 - mesh-lab

place: the host — the lab acquires a consumer

The lab raised an underlay and put nothing on it: correct, and useless, because
the thing it exists to test did not exist. Tier 0 now does, so `place: [host]`
works and a raised scenario finally contains something.

The refusal narrows rather than disappearing. A scenario placing a host and a
substrate is told which half is missing, by name — not that `place:` is
unsupported when half of it now works.

Placement reads back rather than assuming. A file arriving is not a host
working, so the binary is run before it is trusted to answer questions, and what
it reports is read from the machine (ADR 0035). The binary comes from an
explicit path, because the declaration design leaves where artifacts come from
open and a search would harden into the answer by accident.

The integration test that matters is the one asserting the host reports the
MACHINE and not the workstation that placed it. A raised VM and this workstation
differ in every capability — root versus uid 1000, a clean init versus a
degraded one, no docker versus docker, no wireguard versus wg0 — so a host
reporting the wrong machine is obvious here and invisible anywhere else.

And the placed host independently confirms ADR 0031: overlay absent on a freshly
raised machine. The underlay suite already asserted that by looking for
wireguard interfaces; this is a second witness rather than the same check twice.

Two tests failed the moment placement worked, which is what they were for. They
defended "there is nothing to place yet" while that was true; the decision
changed, so they change with it rather than being deleted.

Gate: 75 unit, 20 integration.

This commit is contained in:

jschoubben

2026-08-26 00:41:25 +02:00

parent b015068921

commit 16c13807a9

8 changed files with 377 additions and 12 deletions

									
										scenarios/bootstrap-single.yml
									
		+4
		-1
	
												View File
												
				@@ -14,7 +14,10 @@ machines:

				    at: { segment: hosting, address: [192.0.2.10, "2001:db8:a::10"] }

				    inbound: allow

				# No `place:` yet. The node host it would place does not exist — this lab is being built to

				place:

				  all: [host]

				# The host is placed. Everything above tier 0 is still refused by name — this lab is built to

				# develop it. Declaring it anyway would make the scenario unraisable, and correctly so: the

				# lab refuses declarations it cannot materialise rather than raising a mesh that silently

				# lacks them.