luxolus
/
open-nomad
2
0
Fork 0
Code Issues 1 Pull Requests Packages Releases Wiki Activity
open-nomad/e2e/terraform/packer/README.md

38 lines
1.3 KiB
Markdown
Raw Normal View History

e2e: split Packer build scripts from TF provisioning (#6542) Make a clear split between Packer and Terraform provisioning steps: the scripts in the `packer/linux` directory are run when we build the AMI whereas the stuff in shared are run at Terraform provisioning time. Merging all runtime provisioning scripts into a single script for each of server/client solves the following: * Userdata scripts can't take arguments, they can only be templated and that means we have to do TF escaping in bash/powershell scripts. * TF provisioning scripts race with userdata scripts.
2019-10-25 12:08:24 +00: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
```sh
$ packer --version
E2E: switch packer build files to HCL2 (#9219) Build configuration files need comments, and JSON is also just the worst, isn't it? Upgrade our E2E packer configs to use the new HCL2 syntax.
2020-10-29 14:03:39 +00:00
1.6.4
e2e: split Packer build scripts from TF provisioning (#6542) Make a clear split between Packer and Terraform provisioning steps: the scripts in the `packer/linux` directory are run when we build the AMI whereas the stuff in shared are run at Terraform provisioning time. Merging all runtime provisioning scripts into a single script for each of server/client solves the following: * Userdata scripts can't take arguments, they can only be templated and that means we have to do TF escaping in bash/powershell scripts. * TF provisioning scripts race with userdata scripts.
2019-10-25 12:08:24 +00:00
e2e: use more specific names for OS/distros (#9204) We intend to expand the nightly E2E test to cover multiple distros and platforms. Change the naming structure for "Linux client" to the more precise "Ubuntu Bionic", and "Windows" to "Windows 2016" to make it easier to add new targets without additional refactoring.
2020-10-28 16:58:00 +00:00
# build Ubuntu Bionic AMI
E2E: switch packer build files to HCL2 (#9219) Build configuration files need comments, and JSON is also just the worst, isn't it? Upgrade our E2E packer configs to use the new HCL2 syntax.
2020-10-29 14:03:39 +00:00
$ packer build ubuntu-bionic-amd64.pkr.hcl
Infrastructure for Windows e2e testing (#6584) Includes: * baseline Windows AMI * initial pass at Terraform configurations * OpenSSH for Windows Using OpenSSH is a lot nicer for Nomad developers than winrm would be, plus it lets us avoid passing around the Windows password in the clear. Note that now we're copying up all the provisioning scripts and configs as a zipped bundle because TF's file provisioner dies in the middle of pushing up multiple files (whereas `scp -r` works fine). We're also running all the provisioning scripts inside the userdata by polling for the zip file to show up (gross!). This is because `remote-exec` provisioners are failing on Windows with the same symptoms as: https://github.com/hashicorp/terraform/issues/17728 If we can't fix this, it'll prevent us from having multiple Windows clients running until TF supports count interpolation in the `template_file`, which is planned for a later 0.12 release.
2019-11-19 16:06:10 +00:00
# build Windows AMI
E2E: switch packer build files to HCL2 (#9219) Build configuration files need comments, and JSON is also just the worst, isn't it? Upgrade our E2E packer configs to use the new HCL2 syntax.
2020-10-29 14:03:39 +00:00
$ packer build windows-2016-amd64.pkr.hcl
Infrastructure for Windows e2e testing (#6584) Includes: * baseline Windows AMI * initial pass at Terraform configurations * OpenSSH for Windows Using OpenSSH is a lot nicer for Nomad developers than winrm would be, plus it lets us avoid passing around the Windows password in the clear. Note that now we're copying up all the provisioning scripts and configs as a zipped bundle because TF's file provisioner dies in the middle of pushing up multiple files (whereas `scp -r` works fine). We're also running all the provisioning scripts inside the userdata by polling for the zip file to show up (gross!). This is because `remote-exec` provisioners are failing on Windows with the same symptoms as: https://github.com/hashicorp/terraform/issues/17728 If we can't fix this, it'll prevent us from having multiple Windows clients running until TF supports count interpolation in the `template_file`, which is planned for a later 0.12 release.
2019-11-19 16:06:10 +00:00
```
## Debugging Packer Builds
e2e: Windows provisioning improvements (#9246) Small changes to the Windows 2016 Packer build for debuggability of provisioning: * improve verbosity of powershell error handling * remove unused "tools" installation * use ssh communicator for Packer to improve Packer build times and eliminate deprecated winrm remote access (unavailable from current macOS)
2020-11-09 18:29:40 +00:00
To [debug a Packer build](https://www.packer.io/docs/other/debugging.html)
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.
Infrastructure for Windows e2e testing (#6584) Includes: * baseline Windows AMI * initial pass at Terraform configurations * OpenSSH for Windows Using OpenSSH is a lot nicer for Nomad developers than winrm would be, plus it lets us avoid passing around the Windows password in the clear. Note that now we're copying up all the provisioning scripts and configs as a zipped bundle because TF's file provisioner dies in the middle of pushing up multiple files (whereas `scp -r` works fine). We're also running all the provisioning scripts inside the userdata by polling for the zip file to show up (gross!). This is because `remote-exec` provisioners are failing on Windows with the same symptoms as: https://github.com/hashicorp/terraform/issues/17728 If we can't fix this, it'll prevent us from having multiple Windows clients running until TF supports count interpolation in the `template_file`, which is planned for a later 0.12 release.
2019-11-19 16:06:10 +00:00
e2e: Windows provisioning improvements (#9246) Small changes to the Windows 2016 Packer build for debuggability of provisioning: * improve verbosity of powershell error handling * remove unused "tools" installation * use ssh communicator for Packer to improve Packer build times and eliminate deprecated winrm remote access (unavailable from current macOS)
2020-11-09 18:29:40 +00:00
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:
Infrastructure for Windows e2e testing (#6584) Includes: * baseline Windows AMI * initial pass at Terraform configurations * OpenSSH for Windows Using OpenSSH is a lot nicer for Nomad developers than winrm would be, plus it lets us avoid passing around the Windows password in the clear. Note that now we're copying up all the provisioning scripts and configs as a zipped bundle because TF's file provisioner dies in the middle of pushing up multiple files (whereas `scp -r` works fine). We're also running all the provisioning scripts inside the userdata by polling for the zip file to show up (gross!). This is because `remote-exec` provisioners are failing on Windows with the same symptoms as: https://github.com/hashicorp/terraform/issues/17728 If we can't fix this, it'll prevent us from having multiple Windows clients running until TF supports count interpolation in the `template_file`, which is planned for a later 0.12 release.
2019-11-19 16:06:10 +00:00
* [EC2 instances](https://console.aws.amazon.com/ec2/home?region=us-east-1#Instances:search=Packer;sort=tag:Name)
* [Key pairs](https://console.aws.amazon.com/ec2/v2/home?region=us-east-1#KeyPairs:search=packer;sort=keyName)
* [Security groups](https://console.aws.amazon.com/ec2/v2/home?region=us-east-1#SecurityGroups:search=packer;sort=groupName)