Files
mesh-catalog/modules/distribution
jschoubben 80b8002a94
mesh/delivery ready: it is merged on the Approve
mesh/check failed (8): unit: modules/mesh-delivery-gate.go vet: /var/lib/mesh-build-go-cache/gomod/git.novo…; and 7 more | 80b8002a94f7 on 1c1b03c3a02b
distribution provides artifact-store again beside its new roles, for the running node-engines (issue 1966)
The registry milestone renamed what distribution offers (container-image-registry, oci-artifact-registry,
mesh-artifact-store), as ADR 0632 section 3 decides. The node-engines running on every node are the ones
from before it: they find the store through the provision artifact-store, so they fetch no new build,
including their own successor, and keep running what they ran. ADR 0632 section 2's guarantee (no node loses
the store while its engine reads it the old way) lives in the new indexer's hold, which the running indexer
predates. So this goes against ADR 0632 section 3 for a limited time, at the operator's word (bootstrap of
2026-11-07, no new record): offered again beside the new roles until every node-engine runs the registry
milestone's build, then removed in the next change to distribution.

Claude-Session: https://claude.ai/code/session_01NcbgfFSnn24M3GcqttoU7i
2026-11-07 17:02:47 +01:00
..

distribution

The distribution module of the mesh catalogue: runs the container image registry; holds the seats container-image-registry and oci-artifact-registry, and mesh-artifact-store until its window closes. It provides no provision: the store's address is its listen registry, open to the mesh, which every node-engine finds through the seat's holder (novox/hq ADR 0632). Its seats' list answers what the store holds, read from the store's own files through its container mesh-registry.

Files it does not know

Each directory or archive this module declares says how it treats a file it did not write (ADR 0422, ADR 0416).

  • /var/lib/mesh/registry: everything in it is the program's; the mesh moves nothing out (ADR 0422 §2).
  • /var/lib/mesh-registry: everything in it is the program's; the mesh moves nothing out (ADR 0422 §2).