I am attempting to set up a cluster with a mix of arm64 and amd64 nodes. Inventory:

---
all:
    consul:
      vars:
        consul_autopilot_enable: true
        consul_group_name: consul
      hosts:
        host1:
          consul_node_role: bootstrap
          consul_architecture: amd64
        host2:
          consul_node_role: server
          consul_architecture: arm64

In setup.sh, we should now be using vault operator init instead of vault init and vault operator unseal instead of vault unseal.

Local cluster is dev-level setup; cluster of 1. Remote will be LXD and or Azure/AWS/GCE. Setup Consul Cluster across WAN.

Nomad cluster across region; spans 2 or more DC. Region: SEA; DC: dc1, dc-laptop

Demo application for Golang, Java + Docker workload distributed.

Command center done locally; executed remotely.

// , Currently both Vault and Consul logs are going into /var/log/messages, but for easier external consumption, either by the ELK stack or by Splunk, it would be more convenient if they had separate vault.log and consul.log files.

If someone finds this tool useful, then we should probably rewrite the whole thing in go before adding more functionality.

Consul

SHA256 checksums for Consul 1.0.6
verify the checksums signature file
HashiCorp's GPG key

Nomad

[SHA256 checksums for Nomad 0.7.1 ](https://releases.hashicorp.com/nomad/0.7.1/nomad_0.7