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

Merge pull request #5243 from hashicorp/b-fix-scheduling-links

Browse Source 
website: redirect to new scheduling doc
This commit is contained in:
Mahmood Ali
2019-01-25 11:17:47 -05:00
committed by GitHub
parent 27dd82fe7d b82cab2fe4
commit 47b5dca9a1
2 changed files with 3 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
website/redirects.txt
View File

@@ -85,6 +85,7 @@
/docs/commands/server-join.html /docs/commands/server/join.html
/docs/commands/server-members.html /docs/commands/server/members.html
/docs/runtime/schedulers.html /docs/schedulers.html
/docs/internals/scheduling.html /docs/internals/scheduling/scheduling.html
# Moved /docs/operating-a-job/ -> /guides/operating-a-job/
/docs/operating-a-job /guides/operating-a-job/index.html

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

@@ -81,7 +81,7 @@ Looking at only a single region, at a high level Nomad looks like this:
[![Regional Architecture](/assets/images/nomad-architecture-region.png)](/assets/images/nomad-architecture-region.png)
Within each region, we have both clients and servers. Servers are responsible for
accepting jobs from users, managing clients, and [computing task placements](/docs/internals/scheduling.html).
accepting jobs from users, managing clients, and [computing task placements](/docs/internals/scheduling/scheduling.html).
Each region may have clients from multiple datacenters, allowing a small number of servers
to handle very large clusters.
@@ -132,7 +132,7 @@ ensuring PCI compliant workloads run on appropriate servers.
This has been a brief high-level overview of the architecture of Nomad. There
are more details available for each of the sub-systems. The [consensus protocol](/docs/internals/consensus.html),
[gossip protocol](/docs/internals/gossip.html), and [scheduler design](/docs/internals/scheduling.html)
[gossip protocol](/docs/internals/gossip.html), and [scheduler design](/docs/internals/scheduling/scheduling.html)
are all documented in more detail.
For other details, either consult the code, ask in IRC or reach out to the mailing list.