A two-node bed: a joined node opens the adopted broker over the overlay #28

2026-09-16T23:44:25Z

jschoubben commented

2026-09-16 23:44:25 +00:00

anchor raises the foundation and adopts lavinmq; node2 joins and runs amqp-ping, which requires amqp and provides nothing. Asserts the grant names anchor.internal, a vhost is minted on the far broker, and the consumer stays up. Green with the mesh-controller and mesh-catalog fixes for issue 055.

Includes the operational finding: push the provider node again after adding a cross-node consumer (a provision secret is minted composing the consumer; the provider only reads it). Silent-failure edge opened as hq issue 057.

https://claude.ai/code/session_01D6qtiYU3P9jk3pnAXyAFyx

anchor raises the foundation and adopts lavinmq; node2 joins and runs amqp-ping, which requires amqp and provides nothing. Asserts the grant names anchor.internal, a vhost is minted on the far broker, and the consumer stays up. Green with the mesh-controller and mesh-catalog fixes for issue 055. Includes the operational finding: push the provider node again after adding a cross-node consumer (a provision secret is minted composing the consumer; the provider only reads it). Silent-failure edge opened as hq issue 057. https://claude.ai/code/session_01D6qtiYU3P9jk3pnAXyAFyx

jschoubben added 2 commits 2026-09-16 23:44:25 +00:00

A two-node bed: a joined node opening the adopted broker over the overlay (055) 155800bc9a

anchor raises the foundation and adopts lavinmq; node2 joins and runs amqp-ping,
which requires amqp and provides nothing. Asserts the grant names anchor.internal,
a vhost is minted on the far broker, and the consumer stays up. Currently RED: it
caught two real gaps — the broker's amqps port not in the firewall (fixed in
mesh-catalog) and the module broker URL using the public address not the overlay
(issue 055, needs a controller fix). Goes green when 055 is fixed.

https://claude.ai/code/session_01D6qtiYU3P9jk3pnAXyAFyx

The cross-node bed is green: push the provider node after adding the remote consumer b6bf31d4e6

A provision secret is minted as a side-effect of composing the CONSUMER's plan, and the
provider's grant list is a pure read of secrets already issued from it. So a cross-node
consumer's grant exists only after its node is pushed, and the provider's provisioner mints
the vhost only when the provider node is composed again. Push anchor once more after node2,
and the bed passes: amqp-ping on node2 reaches mesh-broker on anchor over the overlay, its
binding names anchor.internal, and its vhost is minted. Proves both halves of issue 055.

https://claude.ai/code/session_01D6qtiYU3P9jk3pnAXyAFyx

jschoubben merged commit a8afe5ce53 into main

2026-09-16 23:44:53 +00:00

jschoubben deleted branch multi-node/cross-node-bed

2026-09-16 23:44:53 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-lab#28