novox/mesh-controller
Archived
9
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Raise a machine's network from what its engine says, once (hq ADR 0241) #113

Merged
mesh-admin merged 2 commits from feat/machine-network-health into main 2026-10-07 18:16:10 +00:00
Conversation 2 Commits 2 Files Changed 10
+966 -9
mesh-admin commented 2026-10-07 17:04:53 +00:00
Contributor
Copy Link
Copy Source

hq ADR 0241, to-be 48 §10 (Phase F), controller half.

  • node_health.network (migration 0077), kept with each statement; node show lists the parts.
  • From every machine's newest statement: machine...rewritten (outside writer of resolv.conf, writer named, names failing folded in as its cost), machine..network (own faults), machine..unreachable (said once at the hub/resolver machine when it is down on the record or 2+ machines agree; waiters raise nothing). Warning; urgent on control node/hub, bus, or when others wait. Cleared on the first statement not saying it.
  • Gate: a rewrite the send did not make, or another machine unreachable → waits (no rollback); a rewrite of a moved module's file → that module's; own network fault → machine as a whole (issue 281).
  • Tests incl. replay of the engine's container drill (raised on the 4th statement, cleared on the 5th).
  • Rollout after mesh-host's PR.

check-here: merge-gate PASS (4 of 4 compose), repo-check PASS.

hq ADR 0241, to-be 48 §10 (Phase F), controller half. - node_health.network (migration 0077), kept with each statement; node show lists the parts. - From every machine's newest statement: machine.<m>.<owner>.rewritten (outside writer of resolv.conf, writer named, names failing folded in as its cost), machine.<m>.network (own faults), machine.<x>.unreachable (said once at the hub/resolver machine when it is down on the record or 2+ machines agree; waiters raise nothing). Warning; urgent on control node/hub, bus, or when others wait. Cleared on the first statement not saying it. - Gate: a rewrite the send did not make, or another machine unreachable → waits (no rollback); a rewrite of a moved module's file → that module's; own network fault → machine as a whole (issue 281). - Tests incl. replay of the engine's container drill (raised on the 4th statement, cleared on the 5th). - Rollout after mesh-host's PR. check-here: merge-gate PASS (4 of 4 compose), repo-check PASS.
mesh-admin added 2 commits 2026-10-07 17:04:53 +00:00
Raise a machine's network from what its engine says, once (hq ADR 0241) 8bcf787258 
A VPN client rewrote the laptop's resolver file and nothing said so. The
engine now states its machine's networking; the controller keeps it with
the machine's health (migration 0077) and raises the rewrite as its own
finding naming the writer, the machine's own faults as machine.<m>.network,
and what several machines cannot reach once, there. The gate waits on a
rewrite it did not make rather than putting back a good build.
Hold the network statement's field names on the controller's side (hq ADR 0241)
mesh/merge-gate pass: builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step; every machine composes with the change as it…
Details
mesh/repo-check pass: its merge-check.sh passed
Details
mesh/delivery superseded: a newer delivery to the same trunk took over its walk
Details
mesh/delivery-group group feat/machine-network-health closed: a member was closed before the group merged
Details
b8bbf9c79f
mesh-admin commented 2026-10-07 17:05:23 +00:00
Author
Contributor
Copy Link
Copy Source

Delivery novox/mesh-controller@b8bbf9c79fd8 — superseded since 2026-10-07T18:35:11Z

Delivery plan — builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step

  • tier 0: mesh-controller
  • tier 1: build-agent
  • tier 2: route-proxy
  • ace: receives build-agent, route-proxy
  • g14: receives build-agent
  • novox: receives mesh-controller, build-agent, route-proxy
  • shanks: receives build-agent
  • build-agent keeps data (ADR 0233): what it holds is backed up before it moves
  • route-proxy provides route: its consumers are sent again after it
  • route-proxy keeps data (ADR 0233): what it holds is backed up before it moves

Group feat/machine-network-health, in order:

Machines

  • mesh-controller on novox: passed — healthy 3 times over 3m58s
  • mesh-controller on the rest running it: sent
  • build-agent on ace: passed — healthy 3 times over 4m3s
  • build-agent on the rest running it: sent

Transitions

  • 2026-10-07 17:05 (new) → proposed (announced): novox/mesh-controller#113's head announced
  • 2026-10-07 17:10 proposed → checked (checked): the verdict names this commit
  • 2026-10-07 17:10 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
  • 2026-10-07 18:16 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
  • 2026-10-07 18:16 published → delivering (go): its walk started: let go by this owner in its group's order, by a person, or on the controller's own path
  • 2026-10-07 18:35 delivering → superseded (superseded): a newer delivery to the same trunk took over its walk

The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.

<!-- mesh-delivery:view --> **Delivery** `novox/mesh-controller@b8bbf9c79fd8` — **superseded** since 2026-10-07T18:35:11Z **Delivery plan** — builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step - tier 0: mesh-controller - tier 1: build-agent - tier 2: route-proxy - ace: receives build-agent, route-proxy - g14: receives build-agent - novox: receives mesh-controller, build-agent, route-proxy - shanks: receives build-agent - build-agent keeps data (ADR 0233): what it holds is backed up before it moves - route-proxy provides route: its consumers are sent again after it - route-proxy keeps data (ADR 0233): what it holds is backed up before it moves **Group** `feat/machine-network-health`, in order: - novox/mesh-controller@b8bbf9c79fd8 before novox/mesh-host@f8ef2de91d03: built by - novox/mesh-host@f8ef2de91d03 before novox/mesh-controller@b8bbf9c79fd8: engine before controller **Machines** - mesh-controller on novox: passed — healthy 3 times over 3m58s - mesh-controller on the rest running it: sent - build-agent on ace: passed — healthy 3 times over 4m3s - build-agent on the rest running it: sent **Transitions** - 2026-10-07 17:05 (new) → proposed (announced): novox/mesh-controller#113's head announced - 2026-10-07 17:10 proposed → checked (checked): the verdict names this commit - 2026-10-07 17:10 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-07 18:16 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-07 18:16 published → delivering (go): its walk started: let go by this owner in its group's order, by a person, or on the controller's own path - 2026-10-07 18:35 delivering → superseded (superseded): a newer delivery to the same trunk took over its walk The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.
mesh-admin commented 2026-10-07 17:10:52 +00:00
Author
Contributor
Copy Link
Copy Source

Merge check at b8bbf9c7

  • mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller, route-proxy)
  • mesh/repo-check: PASS — its merge-check.sh passed

Change plan — builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step

  • tier 0: mesh-controller
  • tier 1: build-agent
  • tier 2: route-proxy
  • ace: receives build-agent, route-proxy
  • g14: receives build-agent
  • novox: receives mesh-controller, build-agent, route-proxy
  • shanks: receives build-agent
  • build-agent keeps data (ADR 0233): what it holds is backed up before it moves
  • route-proxy provides route: its consumers are sent again after it
  • route-proxy keeps data (ADR 0233): what it holds is backed up before it moves

Run by the build seat on g14 as build-1791392710840785725 (builds --log build-1791392710840785725).

--- the gate: build-agent, mesh-controller, route-proxy
mesh-controller: ok, 46 tool(s); WARNING: controller stay(s) up and say(s) not how it is ready — judged by liveness alone, refused from 2026-11-18 (ADR 0240 rule 8)
long-running resources without health: 1
1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-07T17:03:39Z says they run
composing every machine as the mesh is
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
composing every machine with the change
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose)
judged by controller development build against the facts of 2026-10-07T17:03:39Z

machines:
  - a machine (f35): composes
  - holds mesh-dns-resolver (idt): composes
  - holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes
  - a machine (yvbpsm): composes

a merge would rebuild 3 module(s) in 3 tier(s): build-agent, mesh-controller, route-proxy
--- its merge-check.sh (go toolchain)
ok  	github.com/novox/mesh-controller/cmd/mesh-builder	1.033s
ok  	github.com/novox/mesh-controller/cmd/mesh-controller	187.539s
ok  	github.com/novox/mesh-controller/examples/objectstore-provisioner	1.012s
ok  	github.com/novox/mesh-controller/examples/postgres-provisioner	1.016s
ok  	github.com/novox/mesh-controller/examples/redis-provisioner	1.012s
ok  	github.com/novox/mesh-controller/examples/route-proxy	1.186s
ok  	github.com/novox/mesh-controller/internal/artifacts	1.033s
ok  	github.com/novox/mesh-controller/internal/broker	2.335s
ok  	github.com/novox/mesh-controller/internal/builder	1.236s
ok  	github.com/novox/mesh-controller/internal/catalogue	3.528s
ok  	github.com/novox/mesh-controller/internal/conditions	1.956s
ok  	github.com/novox/mesh-controller/internal/envfile	1.026s
ok  	github.com/novox/mesh-controller/internal/facts	1.028s
ok  	github.com/novox/mesh-controller/internal/identity	6.408s
ok  	github.com/novox/mesh-controller/internal/inventory	96.481s
ok  	github.com/novox/mesh-controller/internal/lease	17.705s
ok  	github.com/novox/mesh-controller/internal/licences	5.429s
ok  	github.com/novox/mesh-controller/internal/licences/adapters	1.008s
ok  	github.com/novox/mesh-controller/internal/link	50.540s
ok  	github.com/novox/mesh-controller/internal/lint	1.711s
ok  	github.com/novox/mesh-controller/internal/outward	1.035s
ok  	github.com/novox/mesh-controller/internal/overlay	1.024s
ok  	github.com/novox/mesh-controller/internal/secrets	1.380s
ok  	github.com/novox/mesh-controller/internal/store	3.701s
ok  	github.com/novox/mesh-controller/internal/testbus	1.166s
ok  	github.com/novox/mesh-controller/internal/token	1.015s
**Merge check** at `b8bbf9c7` - `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller, route-proxy) - `mesh/repo-check`: **PASS** — its merge-check.sh passed **Change plan** — builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step - tier 0: mesh-controller - tier 1: build-agent - tier 2: route-proxy - ace: receives build-agent, route-proxy - g14: receives build-agent - novox: receives mesh-controller, build-agent, route-proxy - shanks: receives build-agent - build-agent keeps data (ADR 0233): what it holds is backed up before it moves - route-proxy provides route: its consumers are sent again after it - route-proxy keeps data (ADR 0233): what it holds is backed up before it moves Run by the build seat on g14 as `build-1791392710840785725` (`builds --log build-1791392710840785725`). ``` --- the gate: build-agent, mesh-controller, route-proxy mesh-controller: ok, 46 tool(s); WARNING: controller stay(s) up and say(s) not how it is ready — judged by liveness alone, refused from 2026-11-18 (ADR 0240 rule 8) long-running resources without health: 1 1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here judging 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-07T17:03:39Z says they run composing every machine as the mesh is the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued composing every machine with the change the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose) judged by controller development build against the facts of 2026-10-07T17:03:39Z machines: - a machine (f35): composes - holds mesh-dns-resolver (idt): composes - holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes - a machine (yvbpsm): composes a merge would rebuild 3 module(s) in 3 tier(s): build-agent, mesh-controller, route-proxy --- its merge-check.sh (go toolchain) ok github.com/novox/mesh-controller/cmd/mesh-builder 1.033s ok github.com/novox/mesh-controller/cmd/mesh-controller 187.539s ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.012s ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.016s ok github.com/novox/mesh-controller/examples/redis-provisioner 1.012s ok github.com/novox/mesh-controller/examples/route-proxy 1.186s ok github.com/novox/mesh-controller/internal/artifacts 1.033s ok github.com/novox/mesh-controller/internal/broker 2.335s ok github.com/novox/mesh-controller/internal/builder 1.236s ok github.com/novox/mesh-controller/internal/catalogue 3.528s ok github.com/novox/mesh-controller/internal/conditions 1.956s ok github.com/novox/mesh-controller/internal/envfile 1.026s ok github.com/novox/mesh-controller/internal/facts 1.028s ok github.com/novox/mesh-controller/internal/identity 6.408s ok github.com/novox/mesh-controller/internal/inventory 96.481s ok github.com/novox/mesh-controller/internal/lease 17.705s ok github.com/novox/mesh-controller/internal/licences 5.429s ok github.com/novox/mesh-controller/internal/licences/adapters 1.008s ok github.com/novox/mesh-controller/internal/link 50.540s ok github.com/novox/mesh-controller/internal/lint 1.711s ok github.com/novox/mesh-controller/internal/outward 1.035s ok github.com/novox/mesh-controller/internal/overlay 1.024s ok github.com/novox/mesh-controller/internal/secrets 1.380s ok github.com/novox/mesh-controller/internal/store 3.701s ok github.com/novox/mesh-controller/internal/testbus 1.166s ok github.com/novox/mesh-controller/internal/token 1.015s ```
mesh-admin merged commit 85d664438f into main 2026-10-07 18:16:10 +00:00
mesh-admin deleted branch feat/machine-network-health 2026-10-07 18:16:10 +00:00
This repo is archived. You cannot comment on pull requests.
Reviewers
No Reviewers
Labels
Clear labels
mesh/ready
Reviewed and ready: mesh-delivery merges at the marked head once its checks pass (hq ADR 0364)
No labels
Milestone
No items
No Milestone
Assignees
Clear assignees
agent-ace agent-g14 agent-novox agent-shanks jschoubben mesh-tools miel.truyen nox-agent
No Assignees
1 Participants
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/mesh-controller#113