Why you´re not ready for Containers in Production!
summary
Argues that most enterprises lack production-ready container practices and offers Habitat as a concrete solution: use the Habitat studio to build immutable packages (versioned, hashed) containing only required libs, publish them to a depot, and run them with a supervisor with gossip that provides built‑in service discovery and health API. Packages export to Docker, rkt or Kubernetes, shrink image bloat, embed orchestration, and integrate with Chef/Test Kitchen and Inspec compliance checks for continuous delivery.
AI-written summary · about
chapters (19)
- 0:00Intro
- 1:22A few questions to start with
- 2:06Enterprise Companies
- 3:33Enterprise IT
- 5:54Configuration Management
- 6:36Chef-Infrastructure Automation
- 7:24Real-Life examples
- 8:24Unreal example?
- 11:10What's the value added!
- 13:31Containers in Production environments
- 15:16Container and Config-Management?!
- 17:18Infrastructure first deployments
- 18:24Application first approach
- 20:46Habitat packaging
- 21:56Habitat plan
- 23:01Habitat workflow
- 25:57Habitat Summary
- 28:15What about testing and compliance
- 30:29Chef Automate
related talks
39mSimplifying Container Operations with Habitat
06mDevOpsCon 2016: Interview with Christian Johannsen
44mKubernetes & Habitat
44mContain yourselves
28mHabitat Automation that travels with the app
39mAchieving Cloud Agnostic Application Deployment with Habitat
31mDockerized app in production? YES WE CAN!!
05mIgnite: Introduction to Habitat