diff options
| -rw-r--r-- | doc/architecture.md | 37 |
1 files changed, 33 insertions, 4 deletions
diff --git a/doc/architecture.md b/doc/architecture.md index ee83dca..53032c2 100644 --- a/doc/architecture.md +++ b/doc/architecture.md @@ -100,10 +100,10 @@ You can for instance use an entry in your `~/.ssh/config` that looks like this: ``` Host caribou - HostName 2a01:e0a:c:a720::23 - LocalForward 14646 127.0.0.1:4646 - LocalForward 8501 127.0.0.1:8501 - LocalForward 1389 bottin.service.staging.consul:389 + HostName 2a01:e0a:c:a720::23 + LocalForward 14646 127.0.0.1:4646 + LocalForward 8501 127.0.0.1:8501 + LocalForward 1389 bottin.service.staging.consul:389 ``` Then, in a separate window, launch `./tlsproxy <cluster_name>`: this will @@ -112,6 +112,35 @@ Nomad and Consul on the regular, unencrypted URLs: `http://localhost:4646` for Nomad and `http://localhost:8500` for Consul. Keep this terminal window for as long as you need to access Nomad and Consul on the cluster. +### Setting scheduler config + +Some configuration options have to be tweaked in the orchestrator. Use `nomad orchestrator scheduler set-config` to obtain the following result: + +```bash +$ nomad operator scheduler get-config --json +{ + "KnownLeader": true, + "LastContact": 0, + "LastIndex": 0, + "NextToken": "", + "RequestTime": 0, + "SchedulerConfig": { + "CreateIndex": 5, + "MemoryOversubscriptionEnabled": true, # << THIS + "ModifyIndex": 399239, + "PauseEvalBroker": false, + "PreemptionConfig": { + "BatchSchedulerEnabled": true, # << THIS + "ServiceSchedulerEnabled": true, # << THIS + "SysBatchSchedulerEnabled": true # << THIS + "SystemSchedulerEnabled": true # << THIS + }, + "RejectJobRegistration": false, + "SchedulerAlgorithm": "binpack" + } +} +``` + ### Launching services Stuff should be started in this order: |