open-nomad/e2e/terraform/terraform.tfvars

region               = "us-east-1"
instance_type        = "t3.medium"
server_count         = "3"
client_count         = "4"
windows_client_count = "1"
profile              = "full-cluster"
nomad_enterprise     = true
nomad_acls           = true
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			`region = "us-east-1"`
e2e: use more recent instance type (#8954) Newer EC2 instances are both cheaper and have generally better performance. The dnsmasq configuration had a hard-coded interface name, so in order to accomodate instances with more recent networking that result in so-called predictable interface names, the dnsmasq configuration needs to be replaced at runtime with userdata to select the default interface. 2020-09-23 18:27:52 +00:00			`instance_type = "t3.medium"`
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			`server_count = "3"`
			`client_count = "4"`
e2e: add a Windows client to test runner (#6735) * Adds a constraint to prevent tests from landing on Windows * Improve Terraform output for mixed windows/linux clients * Makes some Windows client config fixes from 0.10.2 testing 2019-11-25 18:31:00 +00:00			`windows_client_count = "1"`
e2e: provision cluster entirely through Terraform (#8748) Have Terraform run the target-specific `provision.sh`/`provision.ps1` script rather than the test runner code which needs to be customized for each distro. Use Terraform's detection of variable value changes so that we can re-run the provisioning without having to re-install Nomad on those specific hosts that need it changed. Allow the configuration "profile" (well-known directory) to be set by a Terraform variable. The default configurations are installed during Packer build time, and symlinked into the live configuration directory by the provision script. Detect changes in the file contents so that we only upload custom configuration files that have changed between Terraform runs 2020-09-18 15:27:24 +00:00			`profile = "full-cluster"`
e2e: add flag to bootstrap Nomad ACLs (#8961) Adds a `nomad_acls` flag to our Terraform stack that bootstraps Nomad ACLs via a `local-exec` provider. There's no way to set the `NOMAD_TOKEN` in the Nomad TF provider if we're bootstrapping in the same Terraform stack, so instead of using `resource.nomad_acl_token`, we also bootstrap a wide-open anonymous policy. The resulting management token is exported as an environment var with `$(terraform output environment)` and tests that want stricter ACLs will be able to write them using that token. This should also provide a basis to do similar work with Consul ACLs in the future. 2020-09-28 13:22:36 +00:00			`nomad_enterprise = true`
			`nomad_acls = true`