luxolus
/
open-nomad
2
0
Fork 0
Code Issues 1 Pull Requests Packages Releases Wiki Activity

Merge pull request #3347 from hashicorp/docs-federated-ports 

Mention network connectivity in federation guide
This commit is contained in:
Michael Schurter 2017-10-11 16:28:10 -07:00 committed by GitHub
parent 8c1a97765e 4862ea60f8
commit 976ed8d4bc
1 changed files with 10 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
website/source/guides/cluster/federation.md
View File

@ -13,8 +13,14 @@ Because Nomad operates at a regional level, federation is part of Nomad core.
Federation enables users to submit jobs or interact with the HTTP API targeting
any region, from any server, even if that server resides in a different region.
Federating multiple Nomad clusters is as simple as joining servers. From any
server in one region, issue a join command to a server in a remote region:
Federating multiple Nomad clusters requires network connectivity between the
clusters. Servers in each cluster must be able to communicate over [RPC and
Serf][ports]. Federated clusters are expected to communicate over WANs, so they
do not need the same low latency as servers within a region.
Once Nomad servers are able to connect, federating is as simple as joining the
servers. From any server in one region, issue a join command to a server in a
remote region:
```shell
$ nomad server-join 1.2.3.4:4648
@ -26,3 +32,5 @@ enough to join just one known server.
If bootstrapped via Consul and the Consul clusters in the Nomad regions are
federated, then federation occurs automatically.
[ports]: /guides/cluster/requirements.html#ports-used