Eliminated 'consul' from all paths; misc. edits; wrap text at 80 characters
This commit is contained in:
Rob Genova
parent
270391b4b3
commit
3ecaa4e499
|
|
@ -1,14 +0,0 @@
|
|||
---
|
||||
layout: "docs"
|
||||
page_title: "Consul Enterprise Automated Backups"
|
||||
sidebar_current: "docs-consul-enterprise-backups"
|
||||
description: |-
|
||||
Consul Enterprise provides a highly available service that manages taking snapshots, rotation and sending backup files offsite to Amazon S3.
|
||||
|
||||
---
|
||||
|
||||
# Consul Enterprise Automated Backups
|
||||
|
||||
Consul's core snapshot functionality allows you to save and restore the state of the Consul servers for disaster recovery. Snapshots are atomic and point-in-time, and include key/value entries, service catalog, prepared queries, sessions, and ACLs.
|
||||
|
||||
[Consul Enterprise](https://www.hashicorp.com/consul.html) provides a [highly available service](https://www.consul.io/docs/commands/snapshot/agent.html) that integrates with the snapshot API to automatically manage taking snapshots, perform rotation and send backup files offsite to Amazon S3.
|
||||
|
|
@ -1,13 +0,0 @@
|
|||
---
|
||||
layout: "docs"
|
||||
page_title: "Consul Enterprise Advanced Federation"
|
||||
sidebar_current: "docs-consul-enterprise-advanced-federation"
|
||||
description: |-
|
||||
Consul Enterprise enables you to federate Consul datacenters together on a pairwise basis, enabling partially-connected network topologies like hub-and-spoke.
|
||||
---
|
||||
|
||||
# Consul Enterprise Advanced Federation
|
||||
|
||||
Consul's core federation capability uses the same gossip mechanism that is used for a single datacenter. This requires that every server from every datacenter be in a fully connected mesh with an open gossip port (8302/tcp and 8302/udp) and an open server RPC port (8300/tcp). For organizations with large numbers of datacenters, it becomes difficult to support a fully connected mesh. It is often 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](https://www.consul.io/docs/guides/areas.html) that allows you 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 requests for remote resources (in spite of the partially-connected nature of the topology as a whole). Consul datacenters can simultaneously participate in both network areas and the existing WAN pool, which eases migration.
|
||||
|
|
@ -1,20 +0,0 @@
|
|||
---
|
||||
layout: "docs"
|
||||
page_title: "Consul Enterprise"
|
||||
sidebar_current: "docs-consul-enterprise"
|
||||
description: |-
|
||||
Consul Enterprise features a number of capabilities beyond the open
|
||||
source offering that may be beneficial in certain workflows.
|
||||
---
|
||||
|
||||
# Consul Enterprise
|
||||
|
||||
Consul Enterprise simplifies operations by automating workflows. It adds support for microservices deployments across complex network topologies. It also increases both scalability and resilience. Features include:
|
||||
|
||||
- [Automated Backups](/docs/consul-enterprise/backups)
|
||||
- [Automated Upgrades](/docs/consul-enterprise/upgrades)
|
||||
- [Enhanced Read Scalability](/docs/consul-enterprise/read-scale)
|
||||
- [Redundancy Zones](/docs/consul-enterprise/redundancy)
|
||||
- [Advanced Federation for Complex Network Topologies](/docs/consul-enterprise/federation)
|
||||
|
||||
These features are part of [Consul Enterprise](https://www.hashicorp.com/consul.html).
|
||||
|
|
@ -1,11 +0,0 @@
|
|||
---
|
||||
layout: "docs"
|
||||
page_title: "Consul Enterprise Enhanced Read Scalability"
|
||||
sidebar_current: "docs-consul-enterprise-read-scale"
|
||||
description: |-
|
||||
Consul Enterprise supports increased read scalability without impacting write latency.
|
||||
---
|
||||
|
||||
# Consul Enterprise Enhanced Read Scalability
|
||||
|
||||
In [Consul Enterprise](https://www.hashicorp.com/consul.html), servers can be explicitly marked as non-voters. Non-voters will receive the replication stream but will not take part in quorum (required by the leader before log entries can be committed). Adding explicit non-voters will [scale reads](https://www.consul.io/docs/guides/autopilot.html#server-read-scaling) without impacting write latency.
|
||||
|
|
@ -1,11 +0,0 @@
|
|||
---
|
||||
layout: "docs"
|
||||
page_title: "Consul Enterprise Redundancy Zones"
|
||||
sidebar_current: "docs-consul-enterprise-redundancy"
|
||||
description: |-
|
||||
Consul Enterprise redundancy zones enable hot standby servers on a per availability zone basis.
|
||||
---
|
||||
|
||||
# Consul Enterprise Redundancy Zones
|
||||
|
||||
[Consul Enterprise](https://www.hashicorp.com/consul.html) [redundancy zones](https://www.consul.io/docs/guides/autopilot.html#redundancy-zones) make it possible to have more servers than availability zones. For example, in an environment with three availability zones it's now possible to run one voter and one non-voter in each availability zone, for a total of six servers. If an availability zone is completely lost, only one voter will be lost, so the cluster remains available. If a voter is lost in an availability zone, Autopilot will promote the non-voter to voter automatically, putting the hot standby server into service quickly.
|
||||
|
|
@ -1,11 +0,0 @@
|
|||
---
|
||||
layout: "docs"
|
||||
page_title: "Consul Enterprise Automated Upgrades"
|
||||
sidebar_current: "docs-consul-enterprise-upgrades"
|
||||
description: |-
|
||||
Consul Enterprise supports an upgrade pattern that allows you to deploy a complete cluster of new servers and then just wait for the upgrade to complete.
|
||||
---
|
||||
|
||||
# Consul Enterprise Automated Upgrades
|
||||
|
||||
[Consul Enterprise](https://www.hashicorp.com/consul.html) supports an [upgrade pattern](https://www.consul.io/docs/guides/autopilot.html#upgrade-migrations) that allows you to deploy a complete cluster of new servers and then just wait for the upgrade to complete. As the new servers join the cluster, server introduction logic checks the version of each Consul server. If the version is higher than the version on the current set of voters, it will avoid promoting the new servers to voters until the number of new servers matches the number of existing servers at the previous version. Once the numbers match, Autopilot will begin to promote new servers and demote old ones.
|
||||
|
|
@ -0,0 +1,19 @@
|
|||
---
|
||||
layout: "docs"
|
||||
page_title: "Consul Enterprise Automated Backups"
|
||||
sidebar_current: "docs-enterprise-backups"
|
||||
description: |-
|
||||
Consul Enterprise provides a highly available service that manages taking snapshots, rotation and sending backup files offsite to Amazon S3.
|
||||
---
|
||||
|
||||
# Consul Enterprise Automated Backups
|
||||
|
||||
Consul's core snapshot functionality allows operators to save and restore the state of
|
||||
the Consul servers for disaster recovery. Snapshots are atomic and
|
||||
point-in-time, and include key/value entries, service catalog, prepared
|
||||
queries, sessions, and ACLs.
|
||||
|
||||
[Consul Enterprise](https://www.hashicorp.com/consul.html) provides a [highly
|
||||
available service](https://www.consul.io/docs/commands/snapshot/agent.html) that
|
||||
integrates with the snapshot API to automatically manage taking snapshots,
|
||||
perform rotation and send backup files offsite to Amazon S3.
|
||||
|
|
@ -0,0 +1,26 @@
|
|||
---
|
||||
layout: "docs"
|
||||
page_title: "Consul Enterprise Advanced Federation"
|
||||
sidebar_current: "docs-enterprise-advanced-federation"
|
||||
description: |-
|
||||
Consul Enterprise enables you to federate Consul datacenters together on a pairwise basis, enabling partially-connected network topologies like hub-and-spoke.
|
||||
---
|
||||
|
||||
# Consul Enterprise Advanced Federation
|
||||
|
||||
Consul's core federation capability uses the same gossip mechanism that is used
|
||||
for a single datacenter. This requires that every server from every datacenter
|
||||
be in a fully connected mesh with an open gossip port (8302/tcp and 8302/udp)
|
||||
and an open server RPC port (8300/tcp). For organizations with large numbers of
|
||||
datacenters, it becomes difficult to support a fully connected mesh. It is often
|
||||
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](https://www.consul.io/docs/guides/areas.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
|
||||
requests for remote resources (in spite of the partially-connected nature of the
|
||||
topology as a whole). Consul datacenters can simultaneously participate in both
|
||||
network areas and the existing WAN pool, which eases migration.
|
||||
|
|
@ -0,0 +1,23 @@
|
|||
---
|
||||
layout: "docs"
|
||||
page_title: "Consul Enterprise"
|
||||
sidebar_current: "docs-enterprise"
|
||||
description: |-
|
||||
Consul Enterprise features a number of capabilities beyond the open source offering that may be beneficial in certain workflows.
|
||||
---
|
||||
|
||||
# Consul Enterprise
|
||||
|
||||
Consul Enterprise simplifies operations by automating workflows. It adds support
|
||||
for microservices deployments across complex network topologies. It also
|
||||
increases both scalability and resilience. Features include:
|
||||
|
||||
- [Automated Backups](/docs/enterprise/backups/index.html)
|
||||
- [Automated Upgrades](/docs/enterprise/upgrades/index.html)
|
||||
- [Enhanced Read Scalability](/docs/enterprise/read-scale/index.html)
|
||||
- [Redundancy Zones](/docs/enterprise/redundancy/index.html)
|
||||
- [Advanced Federation for Complex Network
|
||||
Topologies](/docs/enterprise/federation/index.html)
|
||||
|
||||
These features are part of [Consul
|
||||
Enterprise](https://www.hashicorp.com/consul.html).
|
||||
|
|
@ -0,0 +1,16 @@
|
|||
---
|
||||
layout: "docs"
|
||||
page_title: "Consul Enterprise Enhanced Read Scalability"
|
||||
sidebar_current: "docs-enterprise-read-scale"
|
||||
description: |-
|
||||
Consul Enterprise supports increased read scalability without impacting write latency.
|
||||
---
|
||||
|
||||
# Consul Enterprise Enhanced Read Scalability
|
||||
|
||||
In [Consul Enterprise](https://www.hashicorp.com/consul.html), servers can be
|
||||
explicitly marked as non-voters. Non-voters will receive the replication stream
|
||||
but will not take part in quorum (required by the leader before log entries can
|
||||
be committed). Adding explicit non-voters will [scale
|
||||
reads](https://www.consul.io/docs/guides/autopilot.html#server-read-scaling)
|
||||
without impacting write latency.
|
||||
|
|
@ -0,0 +1,19 @@
|
|||
---
|
||||
layout: "docs"
|
||||
page_title: "Consul Enterprise Redundancy Zones"
|
||||
sidebar_current: "docs-enterprise-redundancy"
|
||||
description: |-
|
||||
Consul Enterprise redundancy zones enable hot standby servers on a per availability zone basis.
|
||||
---
|
||||
|
||||
# Consul Enterprise Redundancy Zones
|
||||
|
||||
[Consul Enterprise](https://www.hashicorp.com/consul.html) [redundancy
|
||||
zones](https://www.consul.io/docs/guides/autopilot.html#redundancy-zones) make
|
||||
it possible to have more servers than availability zones. For example, in an
|
||||
environment with three availability zones it's now possible to run one voter and
|
||||
one non-voter in each availability zone, for a total of six servers. If an
|
||||
availability zone is completely lost, only one voter will be lost, so the
|
||||
cluster remains available. If a voter is lost in an availability zone, Autopilot
|
||||
will promote the non-voter to voter automatically, putting the hot standby
|
||||
server into service quickly.
|
||||
|
|
@ -0,0 +1,19 @@
|
|||
---
|
||||
layout: "docs"
|
||||
page_title: "Consul Enterprise Automated Upgrades"
|
||||
sidebar_current: "docs-enterprise-upgrades"
|
||||
description: |-
|
||||
Consul Enterprise supports an upgrade pattern that allows operators to deploy a complete cluster of new servers and then just wait for the upgrade to complete.
|
||||
---
|
||||
|
||||
# Consul Enterprise Automated Upgrades
|
||||
|
||||
[Consul Enterprise](https://www.hashicorp.com/consul.html) supports an [upgrade
|
||||
pattern](https://www.consul.io/docs/guides/autopilot.html#upgrade-migrations)
|
||||
that allows operators to deploy a complete cluster of new servers and then just wait
|
||||
for the upgrade to complete. As the new servers join the cluster, server
|
||||
introduction logic checks the version of each Consul server. If the version is
|
||||
higher than the version on the current set of voters, it will avoid promoting
|
||||
the new servers to voters until the number of new servers matches the number of
|
||||
existing servers at the previous version. Once the numbers match, Autopilot will
|
||||
begin to promote new servers and demote old ones.
|
||||
|
|
@ -249,23 +249,23 @@
|
|||
|
||||
<hr>
|
||||
|
||||
<li<%= sidebar_current("docs-consul-enterprise") %>>
|
||||
<a href="/docs/consul-enterprise/index.html">Consul Enterprise</a>
|
||||
<li<%= sidebar_current("docs-enterprise") %>>
|
||||
<a href="/docs/enterprise/index.html">Consul Enterprise</a>
|
||||
<ul class="nav">
|
||||
<li<%= sidebar_current("docs-consul-enterprise-backups") %>>
|
||||
<a href="/docs/consul-enterprise/backups">Automated Backups</a>
|
||||
<li<%= sidebar_current("docs-enterprise-backups") %>>
|
||||
<a href="/docs/enterprise/backups/index.html">Automated Backups</a>
|
||||
</li>
|
||||
<li<%= sidebar_current("docs-consul-enterprise-upgrades") %>>
|
||||
<a href="/docs/consul-enterprise/upgrades">Automated Upgrades</a>
|
||||
<li<%= sidebar_current("docs-enterprise-upgrades") %>>
|
||||
<a href="/docs/enterprise/upgrades/index.html">Automated Upgrades</a>
|
||||
</li>
|
||||
<li<%= sidebar_current("docs-consul-enterprise-read-scale") %>>
|
||||
<a href="/docs/consul-enterprise/read-scale">Enhanced Read Scalability</a>
|
||||
<li<%= sidebar_current("docs-enterprise-read-scale") %>>
|
||||
<a href="/docs/enterprise/read-scale/index.html">Enhanced Read Scalability</a>
|
||||
</li>
|
||||
<li<%= sidebar_current("docs-consul-enterprise-redundancy") %>>
|
||||
<a href="/docs/consul-enterprise/redundancy">Redundancy Zones</a>
|
||||
<li<%= sidebar_current("docs-enterprise-redundancy") %>>
|
||||
<a href="/docs/enterprise/redundancy/index.html">Redundancy Zones</a>
|
||||
</li>
|
||||
<li<%= sidebar_current("docs-consul-enterprise-federation") %>>
|
||||
<a href="/docs/consul-enterprise/federation">Advanced Federation</a>
|
||||
<li<%= sidebar_current("docs-enterprise-federation") %>>
|
||||
<a href="/docs/enterprise/federation/index.html">Advanced Federation</a>
|
||||
</li>
|
||||
</ul>
|
||||
</li>
|
||||
|
|
|
|||
Loading…
Reference in New Issue