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

website: update scheduling links

This commit is contained in:
Armon Dadgar 2015-09-19 12:08:42 -07:00
parent 5d091a0536
commit d31202a7ad
2 changed files with 10 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

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

9
website/source/docs/internals/scheduling.html.md
View File

@ -10,10 +10,11 @@ description: |-
Scheduling is a core function of Nomad. It is the process of assigning tasks Scheduling is a core function of Nomad. It is the process of assigning tasks
from jobs to client machines. This process must respect the constraints as declared from jobs to client machines. This process must respect the constraints as declared
in the job, and optimize for resource utilization by bin packing. This page documents in the job, and optimize for resource utilization. This page documents the details
the details of how scheduling works in Nomad to help both users and developers of how scheduling works in Nomad to help both users and developers
build a mental model of how it works. The design is heavily inspired by Google's build a mental model. The design is heavily inspired by Google's
work on [Omega: flexible, scalable schedulers for large compute clusters](http://research.google.com/pubs/pub41684.html) work on both [Omega: flexible, scalable schedulers for large compute clusters](http://research.google.com/pubs/pub41684.html)
and [Large-scale cluster management at Google with Borg](http://research.google.com/pubs/pub43438.html).
~> **Advanced Topic!** This page covers technical details ~> **Advanced Topic!** This page covers technical details
of Nomad. You don't need to understand these details to of Nomad. You don't need to understand these details to