1ec2fecf3f
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.
40 lines
1 KiB
Markdown
40 lines
1 KiB
Markdown
# NAME
|
|
|
|
git-annex extendcluster - add an additional gateway to a cluster
|
|
|
|
# SYNOPSIS
|
|
|
|
git-annex extendcluster gateway clustername
|
|
|
|
# DESCRIPTION
|
|
|
|
This command is used to configure a repository to serve as an additional
|
|
gateway to a cluster. It is run in that repository.
|
|
|
|
The repository this command is run in should have a remote that is a
|
|
gateway to the cluster. The `gateway` parameter is the name of that remote.
|
|
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]] on each gateway.
|
|
See the documentation of that command for details about configuring nodes.
|
|
|
|
# OPTIONS
|
|
|
|
* The [[git-annex-common-options]](1) can be used.
|
|
|
|
# SEE ALSO
|
|
|
|
[[git-annex]](1)
|
|
[[git-annex-initcluster]](1)
|
|
[[git-annex-updatecluster]](1)
|
|
[[git-annex-updateproxy]](1)
|
|
|
|
<https://git-annex.branchable.com/clusters/>
|
|
|
|
# AUTHOR
|
|
|
|
Joey Hess <id@joeyh.name>
|
|
|
|
Warning: Automatically converted into a man page by mdwn2man. Edit with care.
|