Update links to serf
This commit is contained in:
Seth Vargo
parent
661f36ecdf
commit
dee626c6f2
|
|
@ -54,7 +54,7 @@ description: |-
|
|||
Armon Dadgar is the creator of Consul. He researched and developed
|
||||
most of the internals of how Consul works, including the
|
||||
gossip layer, leader election, etc. Armon is also the creator of
|
||||
<a href="https://www.serfdom.io">Serf</a>,
|
||||
<a href="https://www.serf.io">Serf</a>,
|
||||
<a href="https://github.com/armon/statsite">Statsite</a>, and
|
||||
<a href="https://github.com/armon/bloomd">Bloomd</a>.
|
||||
</div>
|
||||
|
|
@ -73,7 +73,7 @@ description: |-
|
|||
Mitchell Hashimoto is also the creator of
|
||||
<a href="https://www.vagrantup.com">Vagrant</a>,
|
||||
<a href="https://www.packer.io">Packer</a>, and
|
||||
<a href="https://www.serfdom.io">Serf</a>.
|
||||
<a href="https://www.serf.io">Serf</a>.
|
||||
</p>
|
||||
</div>
|
||||
</div>
|
||||
|
|
@ -105,7 +105,7 @@ description: |-
|
|||
<p>
|
||||
Ryan Uber is a core contributor to Consul where he works on all
|
||||
facets of Consul. He is also a core committer to
|
||||
<a href="https://www.serfdom.io">Serf</a>,
|
||||
<a href="https://www.serf.io">Serf</a>,
|
||||
<a href="https://www.nomadproject.io">Nomad</a>, and
|
||||
the Consul tools ecosystem, all while being an employee at
|
||||
<a href="https://www.hashicorp.com">HashiCorp</a>.
|
||||
|
|
@ -123,7 +123,7 @@ description: |-
|
|||
James Phillips is a core contributor to Consul where he works on all
|
||||
facets of Consul, including network tomography and prepared
|
||||
queries. He is also a core committer to
|
||||
<a href="https://www.serfdom.io">Serf</a> and
|
||||
<a href="https://www.serf.io">Serf</a> and
|
||||
the Consul tools ecosystem, all while being an employee at
|
||||
<a href="https://www.hashicorp.com">HashiCorp</a>.
|
||||
</p>
|
||||
|
|
|
|||
|
|
@ -35,7 +35,7 @@ See the [Atlas integration guide](/docs/guides/atlas.html) for more details.
|
|||
|
||||
## Q: Does Consul rely on UDP Broadcast or Multicast?
|
||||
|
||||
Consul uses the [Serf](https://www.serfdom.io) gossip protocol which relies on
|
||||
Consul uses the [Serf](https://www.serf.io) gossip protocol which relies on
|
||||
TCP and UDP unicast. Broadcast and Multicast are rarely available in a multi-tenant
|
||||
or cloud network environment. For that reason, Consul and Serf were both
|
||||
designed to avoid any dependence on those capabilities.
|
||||
|
|
|
|||
|
|
@ -54,7 +54,7 @@ of consensus implies the consistency of a replicated state machine. Consensus is
|
|||
in more detail on [Wikipedia](https://en.wikipedia.org/wiki/Consensus_(computer_science)),
|
||||
and our implementation is described [here](/docs/internals/consensus.html).
|
||||
|
||||
* Gossip - Consul is built on top of [Serf](https://www.serfdom.io/) which provides a full
|
||||
* Gossip - Consul is built on top of [Serf](https://www.serf.io/) which provides a full
|
||||
[gossip protocol](https://en.wikipedia.org/wiki/Gossip_protocol) that is used for multiple purposes.
|
||||
Serf provides membership, failure detection, and event broadcast. Our use of these
|
||||
is described more in the [gossip documentation](/docs/internals/gossip.html). It is enough to know
|
||||
|
|
|
|||
|
|
@ -15,10 +15,10 @@ very simple calculation. This allows for many useful applications, such as findi
|
|||
the service node nearest a requesting node, or failing over to services in the next
|
||||
closest datacenter.
|
||||
|
||||
All of this is provided through the use of the [Serf library](https://www.serfdom.io/).
|
||||
All of this is provided through the use of the [Serf library](https://www.serf.io/).
|
||||
Serf's network tomography is based on ["Vivaldi: A Decentralized Network Coordinate System"](http://www.cs.ucsb.edu/~ravenben/classes/276/papers/vivaldi-sigcomm04.pdf),
|
||||
with some enhancements based on other research. There are more details about
|
||||
[Serf's network coordinates here](https://www.serfdom.io/docs/internals/coordinates.html).
|
||||
[Serf's network coordinates here](https://www.serf.io/docs/internals/coordinates.html).
|
||||
|
||||
~> **Advanced Topic!** This page covers the technical details of
|
||||
the internals of Consul. You don't need to know these details to effectively
|
||||
|
|
|
|||
|
|
@ -10,10 +10,10 @@ description: |-
|
|||
|
||||
Consul uses a [gossip protocol](https://en.wikipedia.org/wiki/Gossip_protocol)
|
||||
to manage membership and broadcast messages to the cluster. All of this is provided
|
||||
through the use of the [Serf library](https://www.serfdom.io/). The gossip protocol
|
||||
through the use of the [Serf library](https://www.serf.io/). The gossip protocol
|
||||
used by Serf is based on
|
||||
["SWIM: Scalable Weakly-consistent Infection-style Process Group Membership Protocol"](http://www.cs.cornell.edu/~asdas/research/dsn02-swim.pdf),
|
||||
with a few minor adaptations. There are more details about [Serf's protocol here](https://www.serfdom.io/docs/internals/gossip.html).
|
||||
with a few minor adaptations. There are more details about [Serf's protocol here](https://www.serf.io/docs/internals/gossip.html).
|
||||
|
||||
~> **Advanced Topic!** This page covers technical details of
|
||||
the internals of Consul. You don't need to know these details to effectively
|
||||
|
|
@ -37,7 +37,7 @@ servers to perform cross datacenter requests. The integrated failure detection
|
|||
allows Consul to gracefully handle an entire datacenter losing connectivity, or just
|
||||
a single server in a remote datacenter.
|
||||
|
||||
All of these features are provided by leveraging [Serf](https://www.serfdom.io/). It
|
||||
All of these features are provided by leveraging [Serf](https://www.serf.io/). It
|
||||
is used as an embedded library to provide these features. From a user perspective,
|
||||
this is not important, since the abstraction should be masked by Consul. It can be useful
|
||||
however as a developer to understand how this library is leveraged.
|
||||
|
|
|
|||
|
|
@ -14,9 +14,9 @@ mechanisms that stem from their designs. However, the security mechanisms
|
|||
of Consul have a common goal: to provide
|
||||
[confidentiality, integrity, and authentication](https://en.wikipedia.org/wiki/Information_security).
|
||||
|
||||
The [gossip protocol](/docs/internals/gossip.html) is powered by [Serf](https://www.serfdom.io/),
|
||||
The [gossip protocol](/docs/internals/gossip.html) is powered by [Serf](https://www.serf.io/),
|
||||
which uses a symmetric key, or shared secret, cryptosystem. There are more
|
||||
details on the security of [Serf here](https://www.serfdom.io/docs/internals/security.html).
|
||||
details on the security of [Serf here](https://www.serf.io/docs/internals/security.html).
|
||||
For details on how to enable Serf's gossip encryption in Consul, see the
|
||||
[encryption doc here](/docs/agent/encryption.html).
|
||||
|
||||
|
|
|
|||
|
|
@ -25,6 +25,6 @@ Below are summaries of HashiCorp’s open source projects and a graphic showing
|
|||
|
||||
[Consul](https://www.consul.io/?utm_source=consul&utm_campaign=HashicorpEcosystem) is a HashiCorp tool for service discovery, service registry, and health checks. In the Atlas workflow Consul is configured at the Packer build stage and identifies the service(s) contained in each artifact. Since Consul is configured at the build phase with Packer, when the artifact is deployed with Terraform, it is fully configured with dependencies and service discovery pre-baked. This greatly reduces the risk of an unhealthy node in production due to configuration failure at runtime.
|
||||
|
||||
[Serf](https://www.serfdom.io/?utm_source=consul&utm_campaign=HashicorpEcosystem) is a HashiCorp tool for cluster membership and failure detection. Consul uses Serf’s gossip protocol as the foundation for service discovery.
|
||||
[Serf](https://www.serf.io/?utm_source=consul&utm_campaign=HashicorpEcosystem) is a HashiCorp tool for cluster membership and failure detection. Consul uses Serf’s gossip protocol as the foundation for service discovery.
|
||||
|
||||
[Vagrant](https://www.vagrantup.com/?utm_source=consul&utm_campaign=HashicorpEcosystem) is a HashiCorp tool for managing development environments that mirror production. Vagrant environments reduce the friction of developing a project and reduce the risk of unexpected behavior appearing after deployment. Vagrant boxes can be built in parallel with production artifacts with Packer to maintain parity between development and production.
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@ description: |-
|
|||
|
||||
# Consul vs. Serf
|
||||
|
||||
[Serf](https://www.serfdom.io) is a node discovery and orchestration tool and is the only
|
||||
[Serf](https://www.serf.io) is a node discovery and orchestration tool and is the only
|
||||
tool discussed so far that is built on an eventually-consistent gossip model
|
||||
with no centralized servers. It provides a number of features, including group
|
||||
membership, failure detection, event broadcasts, and a query mechanism. However,
|
||||
|
|
|
|||
Loading…
Reference in a new issue