From 105ae9a56add176ad02ff2bca67d77685b6bf8e2 Mon Sep 17 00:00:00 2001 From: jochens Date: Wed, 30 Sep 2026 13:56:24 +0200 Subject: [PATCH] =?UTF-8?q?Issue=20169:=20network-share=20is=20the=20modul?= =?UTF-8?q?e=20responsible=20for=20a=20node's=20network=20shares=20?= =?UTF-8?q?=E2=80=94=20a=20node=20role?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- .../00-report.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/04-ISSUES/169-a-machine-shares-its-files-and-the-mesh-does-not-know/00-report.md b/04-ISSUES/169-a-machine-shares-its-files-and-the-mesh-does-not-know/00-report.md index 1b44232..addacf0 100644 --- a/04-ISSUES/169-a-machine-shares-its-files-and-the-mesh-does-not-know/00-report.md +++ b/04-ISSUES/169-a-machine-shares-its-files-and-the-mesh-does-not-know/00-report.md @@ -88,7 +88,11 @@ A binding tells a consumer *where* the share is; it does not put the files on it is something done on a machine, and something done on a machine is a module's work — not the host's (the vocabulary stays closed; no `mount` resource kind). -**A consumer-side module, `network-share`,** assigned on the node that wants the files: +**A consumer-side module, `network-share` — the module responsible for setting up the network +shares a node uses** (the operator's framing). A node role, like `node-uplink` or +`node-dns-resolver`: each machine has it at most once, which is a reason for it to hold a +node-scoped seat, so two modules can never both be writing mount units on one machine. Assigned on +the node that wants the files: - `requires nfs-share` (or `smb-share`); several shares on one node are several local names of the requirement (ADR 0094);