open-nomad/e2e/metrics/input
Tim Gross 9f05d62338
E2E with HCP Consul/Vault (#12267)
Use HCP Consul and HCP Vault for the Consul and Vault clusters used in E2E testing. This has the following benefits:

* Without the need to support mTLS bootstrapping for Consul and Vault, we can simplify the mTLS configuration by leaning on Terraform instead of janky bash shell scripting.
* Vault bootstrapping is no longer required, so we can eliminate even more janky shell scripting
* Our E2E exercises HCP, which is important to us as an organization
* With the reduction in configurability, we can simplify the Terraform configuration and drop the complicated `provision.sh`/`provision.ps1` scripts we were using previously. We can template Nomad configuration files and upload them with the `file` provisioner.
* Packer builds for Linux and Windows become much simpler.

tl;dr way less janky shell scripting!
2022-03-18 09:27:28 -04:00
..
cpustress.nomad e2e: run client/allocs metrics tests nightly (#6842) 2019-12-12 12:45:16 -05:00
diskstress.nomad e2e: run client/allocs metrics tests nightly (#6842) 2019-12-12 12:45:16 -05:00
fabio.nomad e2e: update jobs to use new network stanza format 2020-11-23 10:25:30 -06:00
factorial_windows.nomad e2e: run client/allocs metrics nightly tests vs Windows (#6850) 2019-12-16 08:34:17 -05:00
helloworld.nomad e2e: update jobs to use new network stanza format 2020-11-23 10:25:30 -06:00
mem_windows.nomad e2e: run client/allocs metrics nightly tests vs Windows (#6850) 2019-12-16 08:34:17 -05:00
memstress.nomad e2e: run client/allocs metrics tests nightly (#6842) 2019-12-12 12:45:16 -05:00
prometheus.nomad E2E with HCP Consul/Vault (#12267) 2022-03-18 09:27:28 -04:00
simpleweb.nomad remove references to default mbits 2020-11-23 10:32:13 -06:00