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

docs: fixup wording around datacenters and regions on architecture docs

Browse Source 
Part of #10515
This commit is contained in:
Seth Hoenig
2021-05-06 16:18:02 -06:00
parent 6da38b4959
commit a4b22fe8d2
1 changed files with 14 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files

27
website/content/docs/internals/architecture.mdx
View File

@@ -38,10 +38,10 @@ clarify what is being discussed:
which allow Nomad to be flexible in the types of tasks it supports. Tasks
specify their driver, configuration for the driver, constraints, and resources required.
- **Client** - A Client of Nomad is a machine that tasks can be run on. All clients run the
Nomad agent. The agent is responsible for registering with the servers, watching for any
work to be assigned and executing tasks. The Nomad agent is a long lived process which
interfaces with the servers.
- **Client** - A Nomad client is an agent configured to run and manage tasks
using available compute resources on a machine. The agent is responsible for
registering with the servers, watching for any work to be assigned and executing
tasks. The Nomad agent is a long lived process which interfaces with the servers.
- **Allocation** - An Allocation is a mapping between a task group in a job and a client
node. A single job may have hundreds or thousands of task groups, meaning an equivalent
@@ -56,16 +56,17 @@ clarify what is being discussed:
- **Server** - Nomad servers are the brains of the cluster. There is a cluster of servers
per region and they manage all jobs and clients, run evaluations, and create task allocations.
The servers replicate data between each other and perform leader election to ensure high
availability. Servers federate across regions to make Nomad globally aware.
availability. More information about latency requirements for servers can be found
in [Network Topology](/docs/install/production/requirements#network-topology).
- **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.
- **Regions** - Nomad models infrastructure as regions and datacenters. A region will contain
one or more datacenters. A set of servers joined together will represent a single
region. Servers federate across regions to make Nomad globally aware.
- **Datacenters** - Nomad models a datacenter as an abstract grouping of clients within
a region. Nomad clients are not required to be in the same datacenter as the servers
they are joined with, but do need to be in the same region. Datacenters provide
a way to express fault tolerance among jobs as well as isolation of infrastructure.
- **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"