kemko/nomad
1
0
Fork 0
mirror of https://github.com/kemko/nomad.git synced 2026-01-05 18:05:42 +03:00
Code Issues Packages Projects Releases Wiki Activity

Update links to serf

Browse Source
This commit is contained in:
Seth Vargo
2016-08-08 12:47:59 -04:00
parent 0526594813
commit 80e5d00680
3 changed files with 6 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
website/source/community.html.erb
View File

@@ -45,7 +45,7 @@ employees actively contribute to Nomad.
core contributor to:
<a href="https://www.vaultproject.io">Vault</a>,
<a href="https://www.consul.io">Consul</a>,
<a href="https://www.serfdom.io">Serf</a>,
<a href="https://www.serf.io">Serf</a>,
<a href="https://www.terraform.io">Terraform</a>,
and <a href="https://github.com/armon/statsite">Statsite</a>.
</p>
@@ -60,7 +60,7 @@ employees actively contribute to Nomad.
Ryan Uber is a HashiCorp employee and core contributor to Nomad, with a
focus on the agent, API client, and command-line interface. Ryan is also
an active contributor to both <a href="https://www.consul.io">Consul</a>
and <a href="https://www.serfdom.io">Serf</a>.
and <a href="https://www.serf.io">Serf</a>.
</p>
</div>
</div>

6
website/source/docs/internals/gossip.html.md
View File

@@ -10,10 +10,10 @@ description: |-
# Gossip Protocol
Nomad uses a [gossip protocol](https://en.wikipedia.org/wiki/Gossip_protocol)
to manage membership. This is provided through the use of the [Serf library](https://www.serfdom.io/).
to manage membership. This is provided 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"](https://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 Nomad. You do not need to know these details to effectively
@@ -29,7 +29,7 @@ losing connectivity, or just a single server in a remote region. The gossip prot
is also used to detect servers in the same region to perform automatic clustering
via the [consensus protocol](/docs/internals/consensus.html).
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 Nomad. It can be useful
however as a developer to understand how this library is leveraged.

2
website/source/intro/index.html.markdown
View File

@@ -36,7 +36,7 @@ The key features of Nomad are:
* **Operationally Simple**: Nomad ships as a single binary, both for clients and servers,
and requires no external services for coordination or storage. Nomad combines features
of both resource managers and schedulers into a single system. Nomad builds on the strength
of [Serf](https://www.serfdom.io) and [Consul](https://www.consul.io), distributed management
of [Serf](https://www.serf.io) and [Consul](https://www.consul.io), distributed management
tools by [HashiCorp](https://www.hashicorp.com).
* **Multi-Datacenter and Multi-Region Aware**: Nomad models infrastructure as