From 71628ea086652f4d717e7d3a9aa04690efc3f8de Mon Sep 17 00:00:00 2001 From: poll0rz Date: Mon, 19 Oct 2015 21:26:26 +0200 Subject: [PATCH 1/3] Update schedulers - system (PR #287) https://github.com/hashicorp/nomad/pull/287 --- website/source/docs/internals/scheduling.html.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/source/docs/internals/scheduling.html.md b/website/source/docs/internals/scheduling.html.md index d859e6132e4a..3256440b81d9 100644 --- a/website/source/docs/internals/scheduling.html.md +++ b/website/source/docs/internals/scheduling.html.md @@ -55,7 +55,7 @@ Nomad servers run scheduling workers, defaulting to one per CPU core, which are process evaluations. The workers dequeue evaluations from the broker, and then invoke the appropriate scheduler as specified by the job. Nomad ships with a `service` scheduler that optimizes for long-lived services, a `batch` scheduler that is used for fast placement -of batch jobs, and a `core` scheduler which is used for internal maintenance. Nomad can +of batch jobs, a `system` scheduler that is used to run jobs globally (in every node), and a `core` scheduler which is used for internal maintenance. Nomad can be extended to support custom schedulers as well. Schedulers are responsible for processing an evaluation and generating an allocation _plan_. From 7b8591bb854bb6213c81c46ea0c1ef40c8f79ac9 Mon Sep 17 00:00:00 2001 From: poll0rz Date: Mon, 19 Oct 2015 21:30:21 +0200 Subject: [PATCH 2/3] system scheduler (PR #287) https://github.com/hashicorp/nomad/pull/287 --- website/source/docs/jobspec/index.html.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/website/source/docs/jobspec/index.html.md b/website/source/docs/jobspec/index.html.md index a20217d0c780..c1f463d002af 100644 --- a/website/source/docs/jobspec/index.html.md +++ b/website/source/docs/jobspec/index.html.md @@ -28,6 +28,9 @@ job "my-service" { # Spread tasks between us-west-1 and us-east-1 datacenters = ["us-west-1", "us-east-1"] + # run this job globally + type = "system" + # Rolling updates should be sequential update { stagger = "30s" @@ -131,7 +134,7 @@ The `job` object supports the following keys: a task group of the same name. * `type` - Specifies the job type and switches which scheduler - is used. Nomad provides the `service` and `batch` schedulers, + is used. Nomad provides the `service`, `system` and `batch` schedulers, and defaults to `service`. * `update` - Specifies the task update strategy. This requires providing From 991cb29668c068b42be431271e2631b1417c4f55 Mon Sep 17 00:00:00 2001 From: poll0rz Date: Mon, 19 Oct 2015 22:46:10 +0200 Subject: [PATCH 3/3] format long line --- website/source/docs/internals/scheduling.html.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/website/source/docs/internals/scheduling.html.md b/website/source/docs/internals/scheduling.html.md index 3256440b81d9..328502c6c901 100644 --- a/website/source/docs/internals/scheduling.html.md +++ b/website/source/docs/internals/scheduling.html.md @@ -55,8 +55,9 @@ Nomad servers run scheduling workers, defaulting to one per CPU core, which are process evaluations. The workers dequeue evaluations from the broker, and then invoke the appropriate scheduler as specified by the job. Nomad ships with a `service` scheduler that optimizes for long-lived services, a `batch` scheduler that is used for fast placement -of batch jobs, a `system` scheduler that is used to run jobs globally (in every node), and a `core` scheduler which is used for internal maintenance. Nomad can -be extended to support custom schedulers as well. +of batch jobs, a `system` scheduler that is used to run jobs on every node, +and a `core` scheduler which is used for internal maintenance. +Nomad can be extended to support custom schedulers as well. Schedulers are responsible for processing an evaluation and generating an allocation _plan_. The plan is the set of allocations to evict, update, or create. The specific logic used to