From 85418d6c72d137552b102a733058c98bbb8bebd4 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Wed, 25 Sep 2024 12:10:55 -0400 Subject: [PATCH] update --- doc/todo/git-annex_proxies.mdwn | 18 ++++++++++++++++-- 1 file changed, 16 insertions(+), 2 deletions(-) diff --git a/doc/todo/git-annex_proxies.mdwn b/doc/todo/git-annex_proxies.mdwn index df49481cde..79d669b6dc 100644 --- a/doc/todo/git-annex_proxies.mdwn +++ b/doc/todo/git-annex_proxies.mdwn @@ -38,7 +38,7 @@ Planned schedule of work: The difference between having a cluster gateway and direct connections to the nodes is when there are multiple clients. The cluster gateway updates - its location logs to reflect changes in the nodes that get proxies via + its location logs to reflect changes in the nodes that get proxied via it. So it will pick a node that is not full when using size balanced preferred content. If two clients are accessing a node directly without a cluster gateway, that doesn't happen. @@ -53,7 +53,7 @@ Planned schedule of work: the cluster gateway has, without the complication of actually simulating a cluster gateway. - That would not allows simulating a cluster node that is + That would not allow simulating a cluster node that is also accessed directly via another repository. But cluster nodes generally should not be accessed except via the gateway. Still, to allow simulating that, it would be possible to have a new type of connection, @@ -80,6 +80,20 @@ Planned schedule of work: that would require a first-class gateway simulation with its own location log and node selection. + Alternative approach: Let a cluster node be initialized, which is an + overlay over a repository which shares all of its configuration + except for its uuid. Every change to the location log of a cluster + node is immediately propigated to every repository that has a connection + to it. It is also propigated to the underlaying repository. This lets + more than one cluster node be initialized for the same repository, for + when it is in multiple clusters or behind multiple gateways in the same + cluster. + + clusternode mycluster-foo foo + clusternode othercluster-foo foo + + + * sim: Add support for metadata, so preferred content that matches on it will work