How tristanmorgan/nomad-test works
Project Type and Purpose
• This project is a demo/test setup that leverages HashiCorp products – namely Nomad (for scheduling/container orchestration), Consul (for service discovery and DNS resolution), and Vault (for secrets management). It also makes use of Terraform for infrastructure as code.
• The README confirms roles and requirements such as running containers via Docker for Mac, setting up environment variables, and starting the key services in sequence.
• The goal is to demonstrate a local multi-node (even if single-node in practice) infrastructure with trusted configurations and load-balancing (e.g., Fabio) to preview features and interactions among these components.
File Structure
• Top-level directories – “consul”, “nomad”, “vault”, and “terraform” – correspond to the main components.
• Within “terraform”, you see job definitions for Nomad and various HCL configurations, including policies, job definitions, and disabled jobs. This represents declarative infrastructure and job configurations.
• Configuration files for Consul (under consul/config) and executable startup scripts (e.g., start.sh) indicate the initialization process for each component.
• Files such as .rubocop.yml and Gemfile indicate that there might be some Ruby tooling for testing or configuration management, but the core architecture is around the HashiCorp ecosystem.