The controller writes no /etc/hosts (hq ADR 0199) #60

2026-10-05T19:23:27Z

mesh-admin commented

2026-10-05 19:23:27 +00:00

The private network's module stops asking for the node-names fact written into /etc/hosts. /etc/hosts belongs to the node-hosts-file seat's holder; the controller may only ask that holder to register entries (operator, 2026-10-05). All four machines already resolve mesh names through the one resolver (issue 258). The host gives the region back at the next push; the rest of the file is untouched.

Tests: network test inverted (no fact of the network module names /etc/hosts); the region-composition test removed; full suite + vet pass.

The private network's module stops asking for the `node-names` fact written into /etc/hosts. /etc/hosts belongs to the node-hosts-file seat's holder; the controller may only ask that holder to register entries (operator, 2026-10-05). All four machines already resolve mesh names through the one resolver (issue 258). The host gives the region back at the next push; the rest of the file is untouched. Tests: network test inverted (no fact of the network module names /etc/hosts); the region-composition test removed; full suite + vet pass.

mesh-admin added 1 commit 2026-10-05 19:23:28 +00:00

The controller writes no /etc/hosts (hq ADR 0199) 7fa2568ce7

/etc/hosts is the file of the node-hosts-file seat's holder; the controller writes into no file
another seat's holder owns, and asks that holder if it ever needs a line there. The private
network's module stops asking for the node-names fact; every machine already asks the mesh's
one resolver for these names, and the host gives the region back at the next push.

mesh-admin merged commit 6648e4a5c8 into main

2026-10-05 19:23:42 +00:00

mesh-admin deleted branch fix/the-controller-writes-no-hosts-file

2026-10-05 19:23:42 +00:00

mesh-admin commented

2026-10-06 23:09:51 +00:00

Delivery novox/mesh-controller@6648e4a5c8bb — held since 2026-10-06T23:05:28Z

Held for a person: merged without a passing check: only a person decides that it goes on — mesh-delivery.release with why lets it go on.

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

Transitions

2026-10-06 23:05 (new) → proposed (announced): novox/mesh-controller#60 merged; its head was not heard by this owner, so it is made from the forge's word
2026-10-06 23:05 proposed → held (merged-unchecked): merged without a passing check — a verdict known with it is taken first: only a person decides that it goes on

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

**Delivery** `novox/mesh-controller@6648e4a5c8bb` — **held** since 2026-10-06T23:05:28Z Held for a person: merged without a passing check: only a person decides that it goes on — `mesh-delivery.release` with why lets it go on. **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 **Transitions** - 2026-10-06 23:05 (new) → proposed (announced): novox/mesh-controller#60 merged; its head was not heard by this owner, so it is made from the forge's word - 2026-10-06 23:05 proposed → held (merged-unchecked): merged without a passing check — a verdict known with it is taken first: only a person decides that it goes on The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.

mesh-admin referenced this pull request

2026-10-08 18:21:20 +00:00

Keep what a consumer gives up on until a person delivers it again or drops it (hq issue 330, ADR 0264) #159

mesh-tools referenced this pull request

2026-10-21 13:24:25 +00:00

Send a container's supplementary groups only to a node that reports container-groups, holding the module elsewhere (issue 1638, R4d) #422

This repo is archived. You cannot comment on pull requests.

1 Participants

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-controller#60