History

Daniel Greene af4622ac44 set killmode/killsignal in systemd example The default (control-group) kill mode in systemd will kill the associated executors, leading to a commonly seen behavior of nomad client restarts losing all current allocations. setting the KillSignal to SIGINT seems to be a reasonable default, and allows things like leave_on_interrupt to function		2018-01-16 22:22:32 -08:00
..
systemd	set killmode/killsignal in systemd example	2018-01-16 22:22:32 -08:00
upstart	Change /usr/local/bin to /usr/bin	2015-12-03 09:27:03 -08:00
client.hcl	Lots of fixes from @sethvargo	2017-08-01 15:40:36 -07:00
README.md	Separate agent configuration into its own pages	2016-11-02 18:30:00 -04:00
server.hcl	Lots of fixes from @sethvargo	2017-08-01 15:40:36 -07:00

README.md

Dist

The dist folder contains sample configs for various platforms.

Conventions

On unixes we will place agent configs under /etc/nomad and store data under /var/lib/nomad/. You will need to create both of these directories. We assume that nomad is installed to /usr/bin/nomad.

Agent Configs

The following example configuration files are provided:

server.hcl
client.hcl

Place one of these under /etc/nomad depending on the node's role. You should use server.hcl to configure a node as a server (which is responsible for scheduling) or client.hcl to configure a node as a client (which is responsible for running workloads).

Read https://nomadproject.io/docs/agent/configuration/index.html to learn which options are available and how to configure them.

Upstart

On systems using upstart the basic upstart file under upstart/nomad.conf starts and stops the nomad agent. Place it under /etc/init/nomad.conf.

You can control Nomad with start|stop|restart nomad.

Systemd

On systems using systemd the basic systemd unit file under systemd/nomad.service starts and stops the nomad agent. Place it under /etc/systemd/system/nomad.service.

You can control Nomad with systemctl start|stop|restart nomad.