luxolus
/
open-nomad
2
0
Fork 0
Code Issues 1 Pull Requests Packages Releases Wiki Activity
open-nomad/e2e/terraform/packer/ubuntu-bionic-amd64/nomad.service

21 lines
398 B
SYSTEMD
Raw Normal View History

Terraform configs for e2e tests
2018-12-17 17:40:09 +00:00
[Unit]
Description=Nomad Agent
Requires=network-online.target
After=network-online.target
e2e: prevent Ubuntu startup race conditions (#9428) The cloud-init configuration runs on boot, which can result in a race condition between that and service startup. This has caused provisioning failures because Nomad expects the userdata to have configured a host volume directory. Diagnosing this was also compounded by a warning being fired by systemd for the Nomad unit file. * Update the location of the `StartLimitIntervalSec` field to it's post-systemd-230 location. * Ensure that the weekly AMI build is up-to-date to reduce the risk of unexpected system software changes. * Move the host volume to a directory we can set up at AMI build time rather than in userdata.
2020-11-23 17:29:08 +00:00
StartLimitIntervalSec=10
Terraform configs for e2e tests
2018-12-17 17:40:09 +00:00
[Service]
ExecReload=/bin/kill -HUP $MAINPID
docs: sync systemd unit files; update deploy guide 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.
2019-03-19 22:18:12 +00:00
ExecStart=/usr/local/bin/nomad agent -config /etc/nomad.d
KillMode=process
KillSignal=SIGINT
systemd: set a high but non-infinite fd limit
2019-07-02 16:13:24 +00:00
LimitNOFILE=65536
docs: sync systemd unit files; update deploy guide 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.
2019-03-19 22:18:12 +00:00
LimitNPROC=infinity
e2e: fix nomad service for systemd<230
2019-05-08 03:26:04 +00:00
TasksMax=infinity
docs: sync systemd unit files; update deploy guide 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.
2019-03-19 22:18:12 +00:00
Restart=on-failure
RestartSec=2
StartLimitBurst=3
base podman e2e test and provisioning updates (#8104) * initial setup for terrform to install podman task driver podman * Update e2e provisioning to support root podman Excludes setup for rootless podman. updates source ami to ubuntu 18.04 Installs podman and configures podman varlink base podman test ensure client status running revert terraform directory changes * back out random go-discover go mod change * include podman varlink docs * address comments
2020-06-03 18:06:58 +00:00
Terraform configs for e2e tests
2018-12-17 17:40:09 +00:00
[Install]
WantedBy=multi-user.target