Unify trunk on main: initialization → main #3
@@ -0,0 +1,29 @@
|
||||
# Two machines, one mesh.
|
||||
#
|
||||
# The first raises everything from the bundle its host carries and joins the mesh it made. The
|
||||
# second is an ordinary node: it has a host and nothing else, and a person carries it a token.
|
||||
#
|
||||
# This is the first scenario where the mesh is a mesh. Everything before it proved a machine could
|
||||
# talk to a control plane on its own loopback, which proves less than it looks.
|
||||
scenario: two-nodes
|
||||
|
||||
segments:
|
||||
hosting:
|
||||
kind: public
|
||||
cidr: [192.0.2.0/24]
|
||||
|
||||
machines:
|
||||
anchor:
|
||||
at: { segment: hosting, address: [192.0.2.10] }
|
||||
inbound: allow
|
||||
laptop:
|
||||
at: { segment: hosting, address: [192.0.2.20] }
|
||||
inbound: allow
|
||||
|
||||
images:
|
||||
- postgres:17-alpine
|
||||
- cloudamqp/lavinmq:latest
|
||||
- mesh-control:development
|
||||
|
||||
place:
|
||||
all: [host, runtime]
|
||||
Reference in New Issue
Block a user