History

Mahmood Ali 906528c197 Format Terraform files (#11099 ) Also format terraform scripts with hclfmt, equivalent to terraform fmt. I opted not to use terraform fmt, because I didn't want to introduce dev dependency on the terraform CLI. Also, I've optimized the find command to ignore spurious directories (e.g. .git, node_modules) that seem to be populated with too many files! make hclfmt takes 0.3s on my mac down from 7 seconds!		2021-09-01 15:15:06 -04:00
..
aws	Format Terraform files (#11099 )	2021-09-01 15:15:06 -04:00
azure	Format Terraform files (#11099 )	2021-09-01 15:15:06 -04:00
examples	Format Terraform files (#11099 )	2021-09-01 15:15:06 -04:00
gcp	Format Terraform files (#11099 )	2021-09-01 15:15:06 -04:00
shared	Format Terraform files (#11099 )	2021-09-01 15:15:06 -04:00
README.md	Fix Vagrant link in README (#8839 )	2020-09-08 08:45:46 -05:00
Vagrantfile	demo: Fix Vagrantfile when building staging VM for Cloud build.	2020-06-17 12:22:24 +02:00

README.md

Provision a Nomad cluster in the cloud

Use this repo to easily provision a Nomad sandbox environment on AWS, Azure, or GCP with Packer and Terraform. Consul and Vault are also installed (colocated for convenience). The intention is to allow easy exploration of Nomad and its integrations with the HashiCorp stack. This is not meant to be a production ready environment.

Setup

Clone the repo and optionally use Vagrant to bootstrap a local staging environment:

$ git clone git@github.com:hashicorp/nomad.git
$ cd nomad/terraform
$ vagrant up && vagrant ssh

The Vagrant staging environment pre-installs Packer, Terraform, Docker and the Azure CLI.

Provision a cluster

Follow the steps here to provision a cluster on AWS.
Follow the steps here to provision a cluster on Azure.
Follow the steps here to provision a cluster on GCP.

Continue with the steps below after a cluster has been provisioned.

Test

Run a few basic status commands to verify that Consul and Nomad are up and running properly:

$ consul members
$ nomad server members
$ nomad node status

Unseal the Vault cluster (optional)

To initialize and unseal Vault, run:

$ vault operator init -key-shares=1 -key-threshold=1
$ vault operator unseal
$ export VAULT_TOKEN=[INITIAL_ROOT_TOKEN]

The vault init command above creates a single Vault unseal key for convenience. For a production environment, it is recommended that you create at least five unseal key shares and securely distribute them to independent operators. The vault init command defaults to five key shares and a key threshold of three. If you provisioned more than one server, the others will become standby nodes but should still be unsealed. You can query the active and standby nodes independently:

$ dig active.vault.service.consul
$ dig active.vault.service.consul SRV
$ dig standby.vault.service.consul

See the Getting Started guide for an introduction to Vault.

Getting started with Nomad & the HashiCorp stack

Use the following links to get started with Nomad and its HashiCorp integrations: