Issue 149: an adopted machine's data cannot be placed where it is #189

Merged
jschoubben merged 1 commits from issue/149-adopted-data-cannot-be-placed-where-it-is into main 2026-09-29 21:37:35 +00:00
Contributor

ADR 0112 decided that an assignment places a directory and says where an
access's data is; the control plane implements neither. ace's media stack
(a 40 TB ZFS library, plex state on a second disk) cannot be expressed
without writing ace's paths into manifests.

ADR 0112 decided that an assignment places a directory and says where an access's data is; the control plane implements neither. ace's media stack (a 40 TB ZFS library, plex state on a second disk) cannot be expressed without writing ace's paths into manifests.
mesh-admin added 1 commit 2026-09-29 21:04:31 +00:00
ADR 0112 decided that an assignment places a directory and says where an
access's data is; the control plane implements neither. ace's media stack
(a 40 TB ZFS library, plex state on a second disk) cannot be expressed
without writing ace's paths into manifests.
jschoubben merged commit b1bf895688 into main 2026-09-29 21:37:35 +00:00
jschoubben deleted branch issue/149-adopted-data-cannot-be-placed-where-it-is 2026-09-29 21:37:35 +00:00
Sign in to join this conversation.
No Reviewers
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/hq#189