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 limits the number of process and threads you can create within the cgroup it creates for a given service. This is especially limiting if you have a high number of keys Nomad watches from Consul.
Fixes#4649
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
* hclfmt the world
* 2 space indent
* make every example well formed with stanzas and comments
* jsonfmt too
* mdfmt manually
* _ instead of *
* no [links][], only [links][links]
* ordered lists instead of bullets when possible
* lots of wording fixes
* de-contractionization
* add 127.0.0.1 to SANs
* -1 on intentional errors
* -1 on first person
I apologize in advance for the rather long PR, but unfortunately there
is not an easy way to break this up into smaller chunks. This separates
the agent configuration into smaller, more consumable pieces just like
the job specification.
The existing nomad.service is having minor configuration and this change
adds the following:
* Install section that allows nomad to be able enabled in systemd
* Default limit of open files is set to 65536
Danielle Lancashire