Design 42 zfs-owns-zfs: /etc/hostid by the apply, and the lead's answers A-1 to A-26 (issue 1979) #599

2026-11-12T23:20:12Z

mesh-tools commented

2026-11-12 23:20:12 +00:00

Issue 1979, design 42 milestone part zfs-owns-zfs.

04de5c3b: the milestone part and the main file's The zfs module match ADR 0679 version 23 (accepted 2026-11-12): /etc/hostid is written by the module's apply with zgenhostid, guarded by the pool's label, read back at every start and after every write, kept when the module leaves; the call-site test pins zgenhostid -f, zdb -l, zdb -C and wipefs --no-act (§15, §18, §19, §30, §31).
435fe73a, 8c98c27a, 2c129789: 42-milestones/zfs-owns-zfs-lead-answers.md, the lead's answers to the prepare's 12 design questions and 12 places where design and code disagree (A-1..A-24), and two met since (A-25, A-26), each against 00-META/principles.md.

Not reviewed by architectural domain, by the lead's weighing (rules-are-weighed): the amendment carries an accepted record word for word, and the lead answers are one-line answers the principles settle (playbook 07 step 0b).

go test ./... at the root passes.

Issue 1979, design 42 milestone part zfs-owns-zfs. - 04de5c3b: the milestone part and the main file's *The zfs module* match ADR 0679 version 23 (accepted 2026-11-12): /etc/hostid is written by the module's apply with zgenhostid, guarded by the pool's label, read back at every start and after every write, kept when the module leaves; the call-site test pins zgenhostid -f, zdb -l, zdb -C and wipefs --no-act (§15, §18, §19, §30, §31). - 435fe73a, 8c98c27a, 2c129789: 42-milestones/zfs-owns-zfs-lead-answers.md, the lead's answers to the prepare's 12 design questions and 12 places where design and code disagree (A-1..A-24), and two met since (A-25, A-26), each against 00-META/principles.md. Not reviewed by architectural domain, by the lead's weighing (rules-are-weighed): the amendment carries an accepted record word for word, and the lead answers are one-line answers the principles settle (playbook 07 step 0b). `go test ./...` at the root passes.

mesh-tools added 4 commits 2026-11-12 23:20:13 +00:00

Design 42 zfs-owns-zfs: the apply writes /etc/hostid and reads it back, as ADR 0679 version 17 says 04de5c3b30

No template writes the four binary bytes of /etc/hostid, so it is no resource
and the composer cannot see a second writer: the apply guards it by the pool's
label, reads it back, is unhealthy on a mismatch, and keeps the file on leave.

Design 42 zfs-owns-zfs: the lead's answers to the prepare's 24 questions, each against the principles 435fe73a0f

Design 42 zfs-owns-zfs: A-25, the form search finds ${config-json} 8c98c27a5e

Design 42 zfs-owns-zfs: A-26, a module declares what another resource needs before it

mesh/delivery closed: a newer head of the same pull request

Details

mesh/check pass 2c129789ffe1 on 283363d5cf3a | unit 43 run, 0 kept, 1 skipped | integration 43 run, 0 kept, 1 skipped | composition passed in 46s on 4…

2c129789ff

mesh-tools commented

2026-11-12 23:20:18 +00:00

Delivery novox/hq@4cb9efadae24 — merged since 2026-11-12T23:53:41Z

Source — source.main moved to novox/hq@a5eae7aa0a. Whether it reached the machines is mesh-delivery-view's, derived from source.main, the wants and the haves.

Transitions

2026-11-12 23:28 (new) → proposed (announced): novox/hq#599's head announced
2026-11-12 23:28 proposed → ready (accepted): a verdict names this commit and the trunk's head as its trunk commit, the gate passed or warned, and the repository's own check did not fail; or the check gates no merge (check-gates-merge false)
2026-11-12 23:53 ready → merged (merged): on the trunk its modules follow: merged there

The commit's note under refs/notes/mesh-plan keeps every transition of this change up to its merge: git log --notes=mesh-plan.

**Delivery** `novox/hq@4cb9efadae24` — **merged** since 2026-11-12T23:53:41Z **Source** — source.main moved to novox/hq@a5eae7aa0a68. Whether it reached the machines is `mesh-delivery-view`'s, derived from `source.main`, the wants and the haves. **Transitions** - 2026-11-12 23:28 (new) → proposed (announced): novox/hq#599's head announced - 2026-11-12 23:28 proposed → ready (accepted): a verdict names this commit and the trunk's head as its trunk commit, the gate passed or warned, and the repository's own check did not fail; or the check gates no merge (check-gates-merge false) - 2026-11-12 23:53 ready → merged (merged): on the trunk its modules follow: merged there The commit's note under `refs/notes/mesh-plan` keeps every transition of this change up to its merge: `git log --notes=mesh-plan`.

jschoubben added 1 commit 2026-11-12 23:28:10 +00:00

Design 42 zfs-owns-zfs: A-27 to A-29, met in develop

mesh/delivery merged: source.main moved to novox/hq@a5eae7aa0a68

Details

mesh/check being carried to 4cb9efadae24 on a5eae7aa0a68 | from 283363d5cf3a

4cb9efadae

mesh-tools commented

2026-11-12 23:28:15 +00:00

mesh-delivery: the operator's Approve of this pull request's merge into main is ended: its head 2c129789ff is no longer the pull request's head, or the pull request closed. Nothing is merged on it. The operator is asked again once the checks pass at the new head.

mesh-delivery: the operator's Approve of this pull request's merge into main is ended: its head 2c129789ffe1 is no longer the pull request's head, or the pull request closed. Nothing is merged on it. The operator is asked again once the checks pass at the new head.

mesh-tools merged commit a5eae7aa0a into main

2026-11-12 23:53:40 +00:00

mesh-tools deleted branch design/42-zfs-hostid

2026-11-12 23:53:40 +00:00

Sign in to join this conversation.

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/hq#599