open-nomad/e2e/terraform/packer
Seth Hoenig d2cd605995 dist: place systemd unit options correctly
This PR places StartLimitIntervalSec and StartLimitBurst in the
Unit section of systemd unit files, rather than the Service section.

https://www.freedesktop.org/software/systemd/man/systemd.unit.html

Fixes #10065
2021-02-22 19:23:00 -06:00
..
ubuntu-bionic-amd64 dist: place systemd unit options correctly 2021-02-22 19:23:00 -06:00
windows-2016-amd64 e2e: upgrade terraform consul to 1.9.0 2020-12-03 13:01:14 -06:00
README.md update readme about profiles and packer build 2021-01-25 11:40:26 -05:00
build e2e: Fix build script and pass shellcheck 2021-01-26 09:11:37 -05:00
ubuntu-bionic-amd64.pkr.hcl set sha 2021-01-15 10:49:13 -05:00
windows-2016-amd64.pkr.hcl set sha 2021-01-15 10:49:13 -05:00

README.md

Packer Builds

These builds are run as-needed to update the AMIs used by the end-to-end test infrastructure.

What goes here?

  • steps that aren't specific to a given Nomad build: ex. all Linux instances need jq and awscli.
  • steps that aren't specific to a given EC2 instance: nothing that includes an IP address.
  • steps that infrequently change: the version of Consul or Vault we ship.

Running Packer builds

$ packer --version
1.6.4

# build Ubuntu Bionic AMI
$ ./build ubuntu-bionic-amd64

# build Windows AMI
$ ./build windows-2016-amd64

Debugging Packer Builds

To debug a Packer build you'll need to pass the -debug and -on-error flags. You can then ssh into the instance using the ec2_amazon-ebs.pem file that Packer drops in this directory.

Packer doesn't have a cleanup command if you've run -on-error=abort. So when you're done, clean up the machine by looking for "Packer" in the AWS console: