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

Merge pull request #3059 from hashicorp/d-minor-doc-updates-2 

Minor doc updates
This commit is contained in:
Rob Genova 2017-08-21 11:20:26 -07:00 committed by GitHub
parent 14bae424e1 f6b072dd8e
commit 9933ea3a2c
2 changed files with 12 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
website/source/docs/internals/architecture.html.md
View File

@ -60,13 +60,14 @@ clarify what is being discussed:
The servers replicate data between each other and perform leader election to ensure high
availability. Servers federate across regions to make Nomad globally aware.
* **Regions and Datacenters** - Nomad models infrastructure as regions and datacenters.
Regions may contain multiple datacenters. For example, you may have a `US` region with the
`us-east-1` and `us-west-1` datacenters, connected to the `EU` region with the `eu-fr-1` and
`eu-uk-1` datacenters. Servers are assigned to regions and manage all state for the region and
make scheduling decisions within that region. When multiple regions are federated together,
requests that are made between them are forwarded to the appropriate servers. Data is _not_
replicated between regions.
* **Regions and Datacenters** - Nomad models infrastructure as regions and
datacenters. Regions may contain multiple datacenters. Servers are assigned to
a specific region, managing state and making scheduling decisions within that
region. Multiple regions can be federated together. For example, you may
have a `US` region with the `us-east-1` and `us-west-1` datacenters,
connected to the `EU` region with the `eu-fr-1` and `eu-uk-1` datacenters.
Requests that are made between regions are forwarded to the appropriate servers.
Data is _not_ replicated between regions.
* **Bin Packing** - Bin Packing is the process of filling bins with items in a way that
maximizes the utilization of bins. This extends to Nomad, where the clients are "bins"
@ -93,7 +94,8 @@ At a high level, this setup looks like this:
Regions are fully independent from each other, and do not share jobs, clients, or
state. They are loosely-coupled using a gossip protocol, which allows users to
submit jobs to any region or query the state of any region transparently. Requests
are forwarded to the appropriate server to be processed and the results returned.
are forwarded to the appropriate server to be processed and the results returned.
Data is _not_ replicated between regions.
The servers in each region are all part of a single consensus group. This means
that they work together to elect a single leader which has extra duties. The leader

4
website/source/docs/vault-integration/index.html.md
View File

@ -27,8 +27,8 @@ To use the Vault integration, Nomad servers must be provided a Vault token. This
token can either be a root token or a periodic token with permissions to create
from a token role. The root token is the easiest way to get started, but we
recommend a token role based token for production installations. Nomad servers
will renew the token automatically. Note that the Nomad clients do not need to
be provided with a Vault token.
will renew the token automatically. **Note that the Nomad clients do not need to
be provided with a Vault token.**
### Root Token Integration