open-nomad/e2e/terraform/packer
Mahmood Ali 0853d48927
e2e: Spin clusters with custom url binaries (#10656)
Ease spinning up a cluster, where binaries are fetched from arbitrary
urls.  These could be CircleCI `build-binaries` job artifacts, or
presigned S3 urls.

Co-authored-by: Tim Gross <tgross@hashicorp.com>
2021-05-25 13:47:39 -04:00
..
ubuntu-bionic-amd64 e2e: Spin clusters with custom url binaries (#10656) 2021-05-25 13:47:39 -04:00
windows-2016-amd64 e2e: Spin clusters with custom url binaries (#10656) 2021-05-25 13:47:39 -04:00
build e2e: Spin clusters with custom url binaries (#10656) 2021-05-25 13:47:39 -04:00
README.md
ubuntu-bionic-amd64.pkr.hcl e2e: use public_ip in packer 2021-04-27 15:07:03 -07:00
windows-2016-amd64.pkr.hcl

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: