git-annex/doc/todo/git-annex_proxies.mdwn

192 lines
6.9 KiB
Text
Raw Normal View History

This is a summary todo covering several subprojects, which would extend
git-annex to be able to use proxies which sit in front of a cluster of
repositories.
2024-05-01 16:19:12 +00:00
1. [[design/passthrough_proxy]]
2. [[design/p2p_protocol_over_http]]
3. [[design/balanced_preferred_content]]
4. [[todo/track_free_space_in_repos_via_git-annex_branch]]
5. [[todo/proving_preferred_content_behavior]]
2024-07-01 15:38:29 +00:00
## table of contents
[[!toc ]]
## planned schedule
Joey has received funding to work on this.
Planned schedule of work:
2024-06-27 19:28:10 +00:00
* June: git-annex proxies and clusters
2024-07-01 15:44:54 +00:00
* July, part 1: p2p protocol over http
* July, part 2: git-annex proxy support for exporttree
* August: balanced preferred content
* September: streaming through proxy to special remotes (especially S3)
* October: proving behavior of balanced preferred content with proxies
[[!tag projects/openneuro]]
2024-06-04 11:51:33 +00:00
2024-07-01 15:38:29 +00:00
## work notes
2024-06-04 11:51:33 +00:00
2024-07-26 14:24:23 +00:00
* http server proxying hangs when git-annex copy --to it, maybe other
times. Need to fully test.
2024-07-09 18:30:50 +00:00
2024-07-26 14:24:23 +00:00
* http server proxying needs to get the version negotiated with the proxied
remote and feed that into the proxy function.
* test http server proxying with special remotes
* http server proxying needs to reuse connections to special remotes,
keeping a pool of open ones. Question: How many to keep in the pool?
* Make http server support clusters.
2024-07-25 19:39:57 +00:00
2024-07-24 16:18:51 +00:00
* Support proxying to git remotes using annex+http urls.
(Current documentation says proxying only works with ssh remotes,
so current state is not confusing, but this still needs to be done
eventually.)
2024-07-04 19:18:06 +00:00
## completed items for July's work on p2p protocol over http
2024-07-24 16:19:53 +00:00
* HTTP P2P protocol design [[design/p2p_protocol_over_http]].
2024-07-04 19:18:06 +00:00
2024-07-22 23:50:08 +00:00
* addressed [[doc/todo/P2P_locking_connection_drop_safety]]
2024-07-11 15:50:44 +00:00
* implemented server and client for HTTP P2P protocol
* added git-annex p2phttp command to serve HTTP P2P protocol
2024-07-23 19:37:36 +00:00
* Make git-annex p2phttp support https.
2024-07-24 16:19:53 +00:00
* Allow using annex+http urls in remote.name.annexUrl
2024-07-26 14:24:23 +00:00
* Make http server support proxying.
2024-07-24 15:13:37 +00:00
## items deferred until later for p2p protocol over http
* `git-annex p2phttp` could support systemd socket activation. This would
allow making a systemd unit that listens on port 80.
* `git-annex p2phttp` could serve `.git/annex/p2phttp/.well-known/`,
allowing it to be used by an ACME client to get certificates.
2024-07-02 20:16:37 +00:00
## items deferred until later for [[design/passthrough_proxy]]
2024-07-01 15:29:04 +00:00
* Check annex.diskreserve when proxying for special remotes
to avoid the proxy's disk filling up with the temporary object file
cached there.
* Resuming an interrupted download from proxied special remote makes the proxy
re-download the whole content. It could instead keep some of the
object files around when the client does not send SUCCESS. This would
use more disk, but without streaming, proxying a special remote already
needs some disk. And it could minimize to eg, the last 2 or so.
The design doc has some more thoughts about this.
* Streaming download from proxied special remotes. See design.
2024-07-01 15:29:04 +00:00
(Planned for September)
2024-06-27 16:57:08 +00:00
2024-07-01 15:33:07 +00:00
* When an upload to a cluster is distributed to multiple special remotes,
a temporary file is written for each one, which may even happen in
parallel. This is a lot of extra work and may use excess disk space.
It should be possible to only write a single temp file.
(With streaming this won't be an issue.)
2024-06-27 17:40:09 +00:00
* Indirect uploads when proxying for special remote
(to be considered). See design.
* Getting a key from a cluster currently picks from amoung
the lowest cost remotes at random. This could be smarter,
eg prefer to avoid using remotes that are doing other transfers at the
same time.
* The cost of a proxied node that is accessed via an intermediate gateway
is currently the same as a node accessed via the cluster gateway.
To fix this, there needs to be some way to tell how many hops through
gateways it takes to get to a node. Currently the only way is to
guess based on number of dashes in the node name, which is not satisfying.
Even counting hops is not very satisfying, one cluster gateway could
be much more expensive to traverse than another one.
If seriously tackling this, it might be worth making enough information
available to use spanning tree protocol for routing inside clusters.
2024-06-25 21:50:22 +00:00
2024-06-12 15:55:18 +00:00
* Optimise proxy speed. See design for ideas.
2024-06-04 11:51:33 +00:00
2024-06-12 15:55:18 +00:00
* Use `sendfile()` to avoid data copying overhead when
`receiveBytes` is being fed right into `sendBytes`.
2024-06-25 21:26:26 +00:00
Library to use:
<https://hackage.haskell.org/package/hsyscall-0.4/docs/System-Syscall.html>
2024-06-04 11:51:33 +00:00
2024-06-12 15:55:18 +00:00
* Support using a proxy when its url is a P2P address.
(Eg tor-annex remotes.)
2024-06-23 16:31:00 +00:00
2024-07-01 15:38:29 +00:00
## completed items for June's work on [[design/passthrough_proxy]]:
2024-06-23 20:38:01 +00:00
* UUID discovery via git-annex branch. Add a log file listing UUIDs
accessible via proxy UUIDs. It also will contain the names
of the remotes that the proxy is a proxy for,
from the perspective of the proxy. (done)
* Add `git-annex updateproxy` command (done)
* Remote instantiation for proxies. (done)
* Implement git-annex-shell proxying to git remotes. (done)
* Proxy should update location tracking information for proxied remotes,
so it is available to other users who sync with it. (done)
2024-06-27 19:28:10 +00:00
* Implement `git-annex initcluster` and `git-annex updatecluster` commands (done)
2024-06-23 20:38:01 +00:00
* Implement cluster UUID insertation on location log load, and removal
on location log store. (done)
* Omit cluster UUIDs when constructing drop proofs, since lockcontent will
always fail on a cluster. (done)
* Don't count cluster UUID as a copy in numcopies checking etc. (done)
* Tab complete proxied remotes and clusters in eg --from option. (done)
* Getting a key from a cluster should proxy from one of the nodes that has
it. (done)
* Implement upload with fanout to multiple cluster nodes and reporting back
additional UUIDs over P2P protocol. (done)
* Implement cluster drops, trying to remove from all nodes, and returning
which UUIDs it was dropped from. (done)
* `git-annex testremote` works against proxied remote and cluster. (done)
don't sync with cluster nodes by default Avoid `git-annex sync --content` etc from operating on cluster nodes by default since syncing with a cluster implicitly syncs with its nodes. This avoids a lot of unncessary work when a cluster has a lot of nodes just in checking if each node's preferred content is satisfied. And it avoids content being sent to nodes individually, so instead syncing with clusters always fanout uploads to nodes. The downside is that there are situations where a cluster's preferred content settings can be met, but those of its nodes are not. Or where a node does not contain a key, but the cluster does, and there are not enough copies of the key yet, so it would be desirable the send it there. I think that's an acceptable tradeoff. These kind of situations are ones where the cluster itself should probably be responsible for copying content to the node. Which it can do much less expensively than a client can. Part of the balanced preferred content design that I will be working on in a couple of months involves rebalancing clusters, so I expect to revisit this. The use of annex-sync config does allow running git-annex sync with a specific node, or nodes, and it will sync with it. And it's also possible to set annex-sync git configs to make it sync with a node by default. (Although that will require setting up an explicit git remote for the node rather than relying on the proxied remote.) Logs.Cluster.Basic is needed because Remote.Git cannot import Logs.Cluster due to a cycle. And the Annex.Startup load of clusters happens too late for Remote.Git to use that. This does mean one redundant load of the cluster log, though only when there is a proxy.
2024-06-25 14:06:28 +00:00
* Avoid `git-annex sync --content` etc from operating on cluster nodes by
default since syncing with a cluster implicitly syncs with its nodes. (done)
* On upload to cluster, send to nodes where its preferred content, and not
to other nodes. (done)
2024-06-25 18:52:47 +00:00
* Support annex.jobs for clusters. (done)
* Add `git-annex extendcluster` command and extend `git-annex updatecluster`
to support clusters with multiple gateways. (done)
* Support proxying for a remote that is proxied by another gateway of
a cluster. (done)
* Support distributed clusters: Make a proxy for a cluster repeat
protocol messages on to any remotes that have the same UUID as
the cluster. Needs extension to P2P protocol to avoid cycles.
(done)
* Proxied cluster nodes should have slightly higher cost than the cluster
gateway. (done)
* Basic support for proxying special remotes. (But not exporttree=yes ones
yet.) (done)
2024-07-01 15:29:04 +00:00
* Tab complete remotes in all relevant commands (done)
* Display cluster and proxy information in git-annex info (done)