How djschnei21/multi-product-integration-demo works
Main Components
• Control Workspace: Represented by the “0_control-workspace” directory. This is the orchestration hub that triggers and manages downstream workspaces.
• Networking: From the “1_networking” directory. This sets up the AWS VPC, subnets, HCP HVN, and the peering connection.
• HCP Clusters: Under “2_hcp-clusters” you have components creating:
• HCP Vault cluster
• HCP Boundary cluster
• HCP Consul cluster
• Vault Auth Config: (“3_vault-auth-config”) – Establishes Vault JWT Auth for Terraform Cloud, integrating Vault with TFC dynamic operations.
• Boundary Config: (“4_boundary-config”) – Configures Boundary, sets up dynamic host catalogs, and integrates with Vault for SSH certificate injection.
• Nomad Cluster: (“5_nomad-cluster”) – Provisions a three-node Nomad server cluster with bootstrapping of ACLs; note the associated Nomad policy template.
• Nomad Nodes: (“6_nomad-nodes”) – Provisions additional worker nodes in two groups (x86 and ARM) for Nomad workloads.
• Workload Deployment: The “workload” directory includes Nomad job definitions for frontend and MongoDB deployments.
• Packer: The “packer” directory handles creation of Nomad server and client AMIs using HCP Packer integrated with Terraform.
• Doormat Prereqs: The “doormat-prereqs” directory is used to set up required AWS sandbox account elements.
Relationships and Data Flows
• Vault Auth Config (for bootstrapping and JWT integration) and
• Boundary Config (using Vault for credential injection).
• That the Nomad Cluster (Nomad servers in an Auto Scaling Group) communicates with:
• Nomad Nodes (the worker nodes) in addition to
• The workload deployments that run Nomad jobs.
• That Packer is used to build AMIs for Nomad’s server and client nodes, interfacing with the Nomad components.
Architectural Patterns
• Modular/multi-workspace design in which each directory corresponds to a separate Terraform workspace – demonstrating separation of concerns.
• “better together” integration pattern where each component (Vault, Boundary, Consul, Nomad) communicates with the others to form the complete demonstrative environment.
• Bootstrapping pattern whereby output from HCP Clusters (for example, the Vault bootstrap token) is used by downstream modules (vault-auth-config, nomad-cluster).
Relevant Technologies and Tools
• Terraform & Terraform Cloud (for orchestration and multi-workspace management)
• AWS networking (VPC, subnets, ASGs)
• HCP Services: Vault, Consul, Boundary, and Packer Registry
• Nomad Enterprise (for scheduling workloads)
• Packer (for building machine images)
• Doormat provider for provisioning the AWS sandbox
Final Reminder
• Every component is clearly marked and documented with labels.
• The goal is to capture all key architectural elements since the environment is modular and each component is tightly coupled to a specific role in the integration story.