Simplifying Containers with Habitat - SD DevOps

Transcript

1. Simplifying Containers with Habitat Andre Elizondo
2. Andre Elizondo Solutions Architect @ Chef @useautomation
3. Agenda Current Problems in the World of Containers An overview of Habitat How Habitat Makes Containers Better Questions & Answers
4. 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/
5. Current Container Pain
6. How do you... Decouple the application build from the final production ready container?
7. How do you... Build immutable infrastructure but allow last mile Application config changes?
8. How do you... Orchestrate the application launch order & topology required?
9. How do you... Build containers with the Minimum Viable OS?
11. Modern Applications Source Code Repo Artifact Bare Metal Container Cloud Instance VM Artifact Repo
12. Build Deploy Manage
13. Starts with a plan
14. Simple, Native, and Declarative pkg_origin=core pkg_name=redis pkg_version=3.2.1 pkg_license=('BSD') pkg_maintainer="The Habitat Maintainers <humans@habitat.sh>" 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
15. https://github.com/docker-library/redis/blob/master/3.2/Dockerfile
16. https://github.com/docker-library/redis/blob/master/3.2/Dockerfile
17. Clean room environment Safe by default Installs dependences Built in a studio
19. 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).
20. Central location Publicly hosted Lightweight channels Stored in a depot
22. Easy pattern Shortcuts Increasing specificity Installed by hab
23. Binaries and Config Metadata Side-by-side Packages Contain
25. Install automatically Keep things running Manage configuration Supervisors run services
26. Print config options 12-Factor style Externally enforced Environment configuration
27. More flexible than environment Universal location Externally enforced File configuration
28. 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.
29. Supervisors form a ring Peers Service Groups Gossip Availability increases with scale
30. Supervisors provide a REST API External Actors Health and Status Supervisor Debugging
31. Supervisors support topologies Dynamic configuration Service group level Uses the ring
32. Supervisors provide update strategies Topology aware Tracks views in the depot Ideal for Continuous Delivery
33. 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.
34. Docker ACI Mesosphere Post-process packages
35. Libraries Operating System Application Traditionally the domain of the OS Vendor Application Libraries Config Changes Bottom to Top Dependency Resolution
36. Application & Libraries Minimized OS Top to Bottom Dependency Resolution
40. 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.
41. Operable Application Containers •Isolated •Immutable •Configurable •Common interface for monitoring health •Rebuild from source •Common packaging •Runtime Independence
42. Automation travels with the application Existing & Cloud Native Software Application Automation
43. It’s all open source Apache License
44. 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/