30db07cccb
The systemd configs spread across our repo were fairly out of sync. This should get them on our best practices. The deployment guide also had some strange things like running Nomad as a non-root user. It would be fine for servers but completely breaks clients. For simplicity I simply removed the non-root user references. |
||
|---|---|---|
| .. | ||
| systemd | ||
| upstart | ||
| README.md | ||
| client.hcl | ||
| server.hcl | ||
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.hclclient.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.