open-nomad/e2e/terraform/packer
Tim Gross 87b3abddd3
e2e: use sockaddr for IP address configuration (#6548)
Update the Consul and Vault configs to take advantage of their
included `go-sockaddr` library for getting the IP addresses we need in
a portable way. This particularly avoids problems with "predictable"
interface names provided by systemd.

Also adds the `sockaddr` binary to the Packer build so we can use it
in our provisioning scripts.
2019-10-25 14:08:38 -04:00
..
linux e2e: use sockaddr for IP address configuration (#6548) 2019-10-25 14:08:38 -04:00
packer.json e2e: use sockaddr for IP address configuration (#6548) 2019-10-25 14:08:38 -04:00
README.md e2e: split Packer build scripts from TF provisioning (#6542) 2019-10-25 08:08:24 -04:00

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.4.4

# build linux AMI
$ packer build packer.json