Simplifying Containers with Habitat Andre Elizondo 

Andre Elizondo Solutions Architect @ Chef @useautomation 

Agenda Current Problems in the World of Containers An overview of Habitat How Habitat Makes Containers Better Questions & Answers 

Habitat Community • Join the Habitat Slack Team - http://slack.habitat.sh/ • Work through the tutorial at https://www.habitat.sh/tutorials/ • Explore Habitat packages on the depot - https://app.habitat.sh/ • Explore the Habitat projects - https://github.com/habitat-sh • Read Habitat Blog posts - https://blog.chef.io/?s=habitat • Join the Habitat Forums - https://forums.habitat.sh/ 

Current Container Pain 

How do you... Decouple the application build from the final production ready container? 

How do you... Build immutable infrastructure but allow last mile Application config changes? 

How do you... Orchestrate the application launch order & topology required? 

How do you... Build containers with the Minimum Viable OS? 

No content

Modern Applications Source Code Repo Artifact Bare Metal Container Cloud Instance VM Artifact Repo 

Build Deploy Manage 

Starts with a plan 

Simple, Native, and Declarative pkg_origin=core pkg_name=redis pkg_version=3.2.1 pkg_license=('BSD') pkg_maintainer="The Habitat Maintainers " pkg_source=http://download.redis.io/releases/${pkg_name}-${pkg_version}.tar.gz pkg_shasum=b2a791c4ea3bb7268795c45c6321ea5abcc24457178373e6a6e3be6372737f23 pkg_bin_dirs=(bin) pkg_build_deps=(core/make core/gcc) pkg_deps=(core/glibc) pkg_svc_run="redis-server $pkg_svc_config_path/redis.config" pkg_expose=(6379) do_build() { make } plan.sh Low abstraction Complete dependencies Declare services Simple functions 

https://github.com/docker-library/redis/blob/master/3.2/Dockerfile 

https://github.com/docker-library/redis/blob/master/3.2/Dockerfile 

Clean room environment Safe by default Installs dependences Built in a studio 

No content

How do you... Decouple the application build from the final production ready container? Provide a “DSL” to describe the application build (plan.sh), and provide an isolated environment (studio) to build the application artifact (Habitat Package). 

Central location Publicly hosted Lightweight channels Stored in a depot 

No content

Easy pattern Shortcuts Increasing specificity Installed by hab 

Binaries and Config Metadata Side-by-side Packages Contain 

No content

Install automatically Keep things running Manage configuration Supervisors run services 

Print config options 12-Factor style Externally enforced Environment configuration 

More flexible than environment Universal location Externally enforced File configuration 

How do you... Build immutable infrastructure but allow last mile Application config changes? Ship the config along side an immutable application artifact. Provide a supervisor to dynamically update the config based on environment or service discovery. 

Supervisors form a ring Peers Service Groups Gossip Availability increases with scale 

Supervisors provide a REST API External Actors Health and Status Supervisor Debugging 

Supervisors support topologies Dynamic configuration Service group level Uses the ring 

Supervisors provide update strategies Topology aware Tracks views in the depot Ideal for Continuous Delivery 

How do you... Orchestrate the application launch order & topology required? Provide config aware, autonomous, self-organizing peers (supervisors) with built in topologies for clustering strategies. 

Docker ACI Mesosphere Post-process packages 

Libraries Operating System Application Traditionally the domain of the OS Vendor Application Libraries Config Changes Bottom to Top Dependency Resolution 

Application & Libraries Minimized OS Top to Bottom Dependency Resolution 

No content

No content

No content

How do you... Build containers with the Minimum Viable OS? Allow applications to declare their runtime dependencies, and resolve those dependencies from the application to the infrastructure. 

Operable Application Containers •Isolated •Immutable •Configurable •Common interface for monitoring health •Rebuild from source •Common packaging •Runtime Independence 

Automation travels with the application Existing & Cloud Native Software Application Automation 

It’s all open source Apache License 

Questions • Join the Habitat Slack Team - http://slack.habitat.sh/ • Work through the tutorial at https://www.habitat.sh/tutorials/ • Explore Habitat packages on the depot - https://app.habitat.sh/ • Explore the Habitat projects - https://github.com/habitat-sh • Read Habitat Blog posts - https://blog.chef.io/?s=habitat • Join the Habitat Forums - https://forums.habitat.sh/