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

reword for clarity; note that data is not replicated between regions

Browse Source
This commit is contained in:
Rob Genova
2017-08-19 00:13:26 +00:00
parent 1c4dc061f8
commit c6f869b04b
1 changed files with 10 additions and 8 deletions
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