Merge pull request #308 from poll0rz/patch-1

Update doc with System Scheduler from PR #287

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, 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

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