Ephemeral Apps with Chef, Terraform, Nomad, and Habitat
summary
A tiny Go HTTP-echo app gets packaged with Habitat (plan, default.toml, run hook), updated to handle graceful shutdown on SIGTERM, and exported to Docker. Terraform provisions a Nomad/Consul cluster; Nomad schedules the Habitat supervisor and hundreds of dynamic-port backends while Consul provides DNS service discovery. An Nginx Habitat service does dynamic upstreams, and the demo scales to 50 then 200 instances in about a second, behind host-local port-80 load balancers — the pipeline is built and it works end-to-end.
AI-written summary · about
chapters (5)
related talks
39mSimplifying Container Operations with Habitat
05mIgnite: Introduction to Habitat
39mAchieving Cloud Agnostic Application Deployment with Habitat
36mMeshing Legacy Systems with Habitat Deployed Components to...
44mNomad, orchestration made in HashiCorp
28mHabitat Automation that travels with the app
45mThe Evolution Of Automation
40mCan an Enterprise Run Habitat? Or Course!
