update todo list for this month

whew that's gonna be a lot
This commit is contained in:
Joey Hess 2024-06-14 15:23:43 -04:00
parent 2028ad02b8
commit 846903e9bb
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
2 changed files with 29 additions and 6 deletions

View file

@ -258,7 +258,10 @@ there.)
When a drop is requested from the cluster's UUID, git-annex-shell drops
from all nodes, as well as from the proxy itself. Only indicating success
if it is able to delete all copies from the cluster.
if it is able to delete all copies from the cluster. This needs
`removeKey` to be extended to return UUIDs that the content was dropped
from in addition to the remote's uuid (both on success and on failure)
so that the local location log can be updated.
It does not fan out lockcontent, instead the client will lock content
on specific nodes. In fact, the cluster UUID should probably be omitted

View file

@ -31,8 +31,7 @@ For June's work on [[design/passthrough_proxy]], implementation plan:
of the remotes that the proxy is a proxy for,
from the perspective of the proxy. (done)
* Add `git-annex updateproxy` command and remote.name.annex-proxy
configuration. (done)
* Add `git-annex updateproxy` command (done)
* Remote instantiation for proxies. (done)
@ -41,12 +40,33 @@ For June's work on [[design/passthrough_proxy]], implementation plan:
* Proxy should update location tracking information for proxied remotes,
so it is available to other users who sync with it. (done)
* Implement `git-annex updatecluster` command (done)
* Basic proxying to special remote support (non-streaming).
* Consider getting instantiated remotes into git remote list.
See design.
* Implement single upload with fanout to proxied remotes.
* Implement upload with fanout and reporting back additional UUIDs over P2P
protocol.
* Implement clusters.
* Don't count cluster UUID as a copy. (Including in `whereis` display.)
* Implement cluster UUID insertation on location log load, and removal
on location log store.
* Getting a key from a cluster should proxy from one of the nodes that has
it, or from the proxy repository itself if it has the key.
* On upload to a cluster, as well as fanout to nodes, if the key is
preferred content of the proxy repository, store it there.
(But not when preferred content is not configured.)
* Implement cluster drops, trying to remove from all nodes, and returning
which UUIDs it was dropped from.
* Omit cluster UUIDs when constructing drop proofs, since lockcontent will
always fail on a cluster.
* Support proxies-of-proxies better, eg foo-bar-baz.
Currently, it does work, but have to run `git-annex updateproxy`
@ -55,7 +75,7 @@ For June's work on [[design/passthrough_proxy]], implementation plan:
proxies like that, and instead automatically generate those from the log.
(With cycle prevention there of course.)
* Cycle prevention. See design.
* Cycle prevention including cluster-in-cluster cycles. See design.
* Optimise proxy speed. See design for ideas.