How Habitat can Boost your Chef Ecosystem
summary
GE Digital replaces heavy Chef cookbooks with Habitat plans inside a custom runtime called Buffet, packaging each service with its dependencies, supervising processes, and using gossip-based discovery. Result: about 100 lines of cookbook code removed, ELK stack convergence drops from 10 to 7 minutes (≈30% faster), disaster recovery restores a cluster in about 3 minutes, rolling upgrades happen one node at a time, and leader election requires at least three Habitat members.
AI-written summary · about
chapters (25)
- 0:00Introduction
- 3:40The problem
- 3:53Three simple steps
- 5:09Stateless vs Stateful
- 6:39What is a Buffet
- 7:25What is an API
- 8:43Clustering in Chef
- 8:56Dynamic Cluster Location in Chef
- 9:10Dependencies
- 9:38Problems
- 10:13Service Discovery
- 10:49Finding a Leader
- 11:27Configuration Change
- 12:35Quick config changes
- 13:35Habitat buffet
- 15:00Habitat vs Chef
- 17:12Better Packaging
- 19:27FasterConvergence
- 23:16Search
- 24:32Finding a Master
- 26:00Demo
- 30:03Intelligent Run Time
- 32:19Habitat Demo
- 35:02Rolling Upgrades
- 38:05Questions
related talks
05mIgnite: Introduction to Habitat
22mLeveraging Chef, Packer, and Habitat for Effortless AMI Deployments
31mHabitat Builder: Cloud Native Application Automation - Elliott Davis & Fletcher Nichol, Chef.io
45mThe Evolution Of Automation
17mEmpowering Strategic Charitable Investments with Automation Science
39mSimplifying Container Operations with Habitat
40mCan an Enterprise Run Habitat? Or Course!
28mHabitat Automation that travels with the app