mirror of
https://github.com/status-im/consul.git
synced 2025-02-22 10:28:31 +00:00
rename refs to areas guide to advanced-federation (#5603)
This commit is contained in:
parent
8ae3447447
commit
9d6e507616
@ -26,7 +26,7 @@ datacenters, so not all servers need to be fully connected. This allows for
|
||||
complex topologies among Consul datacenters like hub/spoke and more general
|
||||
trees.
|
||||
|
||||
Please see the [Network Areas Guide](/docs/guides/areas.html) for more details.
|
||||
Please see the [Network Areas Guide](/docs/guides/advanced-federation.html) for more details.
|
||||
|
||||
## Create Network Area
|
||||
|
||||
|
@ -24,7 +24,7 @@ and relationships can be made between independent pairs of datacenters, so not a
|
||||
need to be fully connected. This allows for complex topologies among Consul datacenters like
|
||||
hub/spoke and more general trees.
|
||||
|
||||
See the [Network Areas Guide](/docs/guides/areas.html) for more details.
|
||||
See the [Network Areas Guide](/docs/guides/advanced-federation.html) for more details.
|
||||
|
||||
```text
|
||||
Usage: consul operator area <subcommand> [options]
|
||||
@ -250,4 +250,4 @@ The output looks like this:
|
||||
Updated area "d2872ec5-68ea-b862-b75d-0bee99aca100"
|
||||
```
|
||||
|
||||
The return code will indicate success or failure.
|
||||
The return code will indicate success or failure.
|
||||
|
@ -17,7 +17,7 @@ desirable to have topologies like hub-and-spoke with central management
|
||||
datacenters and "spoke" datacenters that can't interact with each other.
|
||||
|
||||
[Consul Enterprise](https://www.hashicorp.com/consul.html) offers a [network
|
||||
area mechanism](/docs/guides/areas.html) that allows operators to
|
||||
area mechanism](/docs/guides/advanced-federation.html) that allows operators to
|
||||
federate Consul datacenters together on a pairwise basis, enabling
|
||||
partially-connected network topologies. Once a link is created, Consul agents
|
||||
can make queries to the remote datacenter in service of both API and DNS
|
||||
|
@ -37,7 +37,7 @@ over the WAN. Consul clients make use of resources in federated clusters by
|
||||
forwarding RPCs through the Consul servers in their local cluster, but they
|
||||
never interact with remote Consul servers directly. There are currently two
|
||||
inter-cluster network models: [WAN Gossip (OSS)](/docs/guides/datacenters.html)
|
||||
and [Network Areas (Enterprise)](/docs/guides/areas.html).
|
||||
and [Network Areas (Enterprise)](/docs/guides/advanced-federation.html).
|
||||
|
||||
**LAN Gossip Pool**: A set of Consul agents that have full mesh connectivity
|
||||
among themselves, and use Serf to maintain a shared view of the members of the
|
||||
|
@ -22,7 +22,7 @@ This guide covers the basic form of federating Consul clusters using a single
|
||||
WAN gossip pool, interconnecting all Consul servers.
|
||||
[Consul Enterprise](https://www.hashicorp.com/products/consul/) version 0.8.0 added support
|
||||
for an advanced multiple datacenter capability. Please see the
|
||||
[Advanced Federation Guide](/docs/guides/areas.html) for more details.
|
||||
[Advanced Federation Guide](/docs/guides/advanced-federation.html) for more details.
|
||||
|
||||
## Setup Two Datacenters
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user