mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

set up proxies for cluster nodes that are themselves proxied via a remote

Browse source 
When there are multiple gateways to a cluster, this sets up proxying
for nodes that are accessed via a remote gateway.

Eg, when running in nyc and amsterdam is the remote gateway,
and it has node1 and node2, this sets up proxying for
amsterdam-node1 and amsterdam-node2. A client that has nyc as a remote
will see proxied remotes nyc-amsterdam-node1 and nyc-amsterdam-node2.
This commit is contained in:
Joey Hess 2024-06-26 11:24:55 -04:00
parent 02bf3ddc3f
commit 1ec2fecf3f
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
4 changed files with 43 additions and 12 deletions
Download patch file Download diff file Expand all files Collapse all files

4
doc/git-annex-extendcluster.mdwn
View file

@ -17,8 +17,8 @@ The `clustername` parameter is the name of the cluster.
The next step after running this command is to configure
any additional cluster nodes that this gateway serves to the cluster,
then run [[git-annex-updatecluster]]. See the documentation of
that command for details about configuring nodes.
then run [[git-annex-updatecluster]] on each gateway.
See the documentation of that command for details about configuring nodes.
# OPTIONS

4
doc/git-annex-updatecluster.mdwn
View file

@ -9,8 +9,8 @@ git-annex updatecluster
# DESCRIPTION
This command is used to record the nodes of a cluster in the git-annex
branch. It should be run in the repository that will serve as a gateway
to the cluster.
branch, and set up proxying to the nodes. It should be run in the
repository that will serve as a gateway to the cluster.
It looks at the git config `remote.name.annex-cluster-node` of
each remote. When that is set to the name of a cluster that has been