habitat at docker bud
Download as PPTX, PDF0 likes139 views
Habitat is an open source project that provides tools for building, deploying, and managing applications across platforms. It allows developers to build applications once and run them anywhere by ignoring the underlying platform and packaging applications with all of their dependencies. Habitat provides tools for building applications locally, managing packages in a private registry, and running applications as managed services that can be updated in a zero-downtime way.
![Have a Plan
pkg_name=container_sched_backend
pkg_origin=lnxchk pkg_version="0.1.0" pkg_build_deps=(core/rust)
pkg_deps=(core/glibc core/gcc core/gcc-libs)
pkg_bin_dirs=(bin)
bin="container_sched_backend"
pkg_exports=([out]=cfg.out)
do_build() {
cargo build
}
do_install() {
install -v -D "$PLAN_CONTEXT/../target/debug/$bin" "$pkg_prefix/bin/$binâ
}
pkg_svc_run="$bin"
Metadata
Build
Install
Run](https://image.slidesharecdn.com/2018-walls-habitat-180508130222/85/habitat-at-docker-bud-17-320.jpg)
![Application Configuration File: TOML
[myconfig]
out = "{{cfg.out}}"
color = "{{cfg.color}}"
{{~# if svc.me.leader ~}}
leader = true
{{ else }}
leader = false
{{/if ~}}](https://image.slidesharecdn.com/2018-walls-habitat-180508130222/85/habitat-at-docker-bud-26-320.jpg)
![Set Defaults in Habitat â default.toml
leader = false
out = "out"
color = "greenâ
[tomltable]
var = âvalâ](https://image.slidesharecdn.com/2018-walls-habitat-180508130222/85/habitat-at-docker-bud-31-320.jpg)
habitat at docker bud
- 2. Mandi Walls Technical Community Manager for EMEA @lnxchk mandi@chef.io #habitatsh http://slack.habitat.sh/ Ian Henry @Eeyun___ Habitat Community lead
- 3. Cloud Native Operations with Habitat Habitat Supervisor Habitat Builder BUILD DEPLOY MANAGE Habitat Supervisor PUBLIC ORIGIN PRIVATE ORIGIN
- 4. How Do We Run Applications? âą On a computer âą With an OS âą And some libraries âą And some configuration âą And some way to start it and stop it
- 5. Weâve been moving complexity around rather than reducing it
- 6. Ugh.
- 7. So. Habitat. âą Ignore the underlying platform as much as possible âą Support microservices âą Manage container creep âą Make your workflow smoother https://www.bonanza.com/listings/Premier-Food-Storage-Containers-20-Piece-Set-Grey/443972348
- 8. Stage 1: Build on Local
- 9. What Habitat Gets Your Developers âą Do clean room builds âą Build repetition âą Get the exact versions of libraries you need, not whatever is on the OS âą Build once and run in dev/test/prod on whatever platform
- 10. What Habitat Gets Your Operators âą Defer some decisions to runtime âą Distro agnostic packaging system âą Service runtime and discovery âą Configuration exposed via API âą Signed packages for your organization
- 12. Building Your Own Apps âą Build your apps from source âą Include libraries and runtime as source or binaries âą Habitat team and community publish hundreds of packages âą Get the newest (or oldest!?!) versions of libraries you need âą Specify the same build process using standard tools
- 13. Leave it to Builder âą Gives you a build service âą And an artifact store âą Including private repos âą Check code in to GitHub, let Builder create your artifact CLOUD/INFRA BUILDSERVICE APPLICATION RUNTIME APPLICATIONSUPERVISION APPLICATION & DATA SERVICES SCHEDULING AND ORCHESTRATION APPLICATION CODE ARTIFACTSTORE
- 14. Hook Your GitHub Repo to Builder âą Add habitat files to your repo âą Hook the Habitat app to your repo âą Builder can take care of building your Habitat artifacts and also integrates to Docker Hub
- 16. Habitat Files Travel with the App Code
- 17. Have a Plan pkg_name=container_sched_backend pkg_origin=lnxchk pkg_version="0.1.0" pkg_build_deps=(core/rust) pkg_deps=(core/glibc core/gcc core/gcc-libs) pkg_bin_dirs=(bin) bin="container_sched_backend" pkg_exports=([out]=cfg.out) do_build() { cargo build } do_install() { install -v -D "$PLAN_CONTEXT/../target/debug/$bin" "$pkg_prefix/bin/$binâ } pkg_svc_run="$bin" Metadata Build Install Run
- 18. Habitat Builder âą Build services including private repos! âą You can share plans with the Depot, and other hab users share theirs âą Has team namespacing âą The core plans are those built by the Habitat team âą https://bldr.habitat.sh/
- 19. Build Output âą By default, itâs a hart â a compressed tarball with some metadata and a signature âą You can export to other formats, like Docker containers âą The hart itself it runnable
- 20. Updating Configuration at Runtime âą Update all or part of the configuration while the apps are running âą Send the update to a member of the mesh and they will all update sudo hab config apply --peer 172.31.2.123 container_sched_backend.stage 2 new.toml
- 21. Shortcut for common platforms: Scaffolding âą Default core-built dependencies for common runtimes âą Ruby and Node so farpkg_name=MY_APP pkg_origin=MY_ORIGIN pkg_version=MY_VERSION pkg_scaffolding=core/scaffolding-ruby https://www.habitat.sh/docs/concepts-scaffolding/
- 22. Builder Demo âą Training app in node âą Repository in Github Make changes on gh or using regular push âą Linked to Builder for creation of habitat artifacts âą Export to Docker Hub âą Run Docker container on CentOS and Ubuntu âą Run hart natively
- 23. Join Us! âą On Slack! http://slack.habitat.sh âą Online! With Tutorials! https://www.habitat.sh/ âą On Github! https://github.com/habitat-sh
- 24. New Stuff âą Updates from KubeCon https://blog.chef.io/2018/05/02/product-updates-habitat- goes-to-kubecon-eu/ âą Azure Deployments with Habitat, ACR and AKS https://blog.chef.io/2018/05/07/deploy-your-applications-to- azure-using-habitat-azure-container-registry-and-azure- container-service/ âą These Slides https://www.slideshare.net/lnxchk/habitat-at-docker-bud
- 25. Slide parking lot Other unused slides
- 26. Application Configuration File: TOML [myconfig] out = "{{cfg.out}}" color = "{{cfg.color}}" {{~# if svc.me.leader ~}} leader = true {{ else }} leader = false {{/if ~}}
- 27. Runtime âą The hab runtime includes management, service discovery, other features âą The habs in your application create a mesh so they can talk to each other âą You can even update your application via the mesh without restarting every application manually
- 28. Running a Hart sudo hab start lnxchk/container_sched_backend --peer 172.31.13.250 --topology leader âą The same hart runs on multiple distros â no need for other packages âą Once hooked together, the supervisors will have a leader election âą If instances move in or out of the mesh, a new election will occur after a timeout âą Updates are persistent and stored in metadata on the hosts /hab/data/services
- 29. Caveat - Internet âą You can build your own stuff inside your own network, sort of, when itâs all on one machine âą There may eventually be a private depot server âą For now, hab and its components need internet access
- 30. Configuration âą Can be manipulated at runtime âą Also travels with the app âą Templating engine included
- 31. Set Defaults in Habitat â default.toml leader = false out = "out" color = "greenâ [tomltable] var = âvalâ
Editor's Notes
- #5: On prem or in the cloud. Or in a hybrid cloud. Or in containers. Or something. On Ubuntu. Or on Red Hat. Or on CentOS if itâs not production. Or that one weird team that wants something else. OS, distribution, version? Packaging type? Initialization system type? Omg itâs systemd Where does it live? /opt /bin /company How to config? .conf .json .yml .dat What version of the language runtime??
- #7: Ouch. Is this something we expect? Should we expect it? How do we get it? We need a different kind of abstraction to accomplish this goal.
- #8: Habitat aims to take the chaos and snowflakeness out of running applications With the move towards microservices and increasingly distributed systems, taming this chaos is important The application comes first
- #10: Single build can be run natively or in containers Run one, run many. Hook them together via the supervisor or not Donât have to care whatâs already on the target systems. Bring all your stuff with you â and only what you need Share your plan.sh files with others via depot
- #13: Packages totally won. But added a bunch of complexity where they were meant to alleviate it Some upstream will be hard to build, and the provider may recommend packages Habitat community is helping with that
- #27: This is the applicationâs configuration file, as templated for habitat. There are three overall variables âoutâ and âcolorâ are configured from the environment. There are defaults that live with the habitat configuration that will be used unless a new value is passed at runtime. The âleaderâ variable is set based on the service. The configuration file is rewritten when an action comes to the running service â either an explicit new configuration is applied, a leader election takes place, or the application is updated to a new version