Juju & Model Driven Operations: An Introduction
summary
Juju models deployed software and ships a lifecycle manager plus a store of Charmed operators — packaged ops code that handles backups, upgrades, relations and Day 2 actions — so you can deploy the same charms across AWS, Azure, bare metal or Kubernetes. Canonical maintains Juju core (about 22 headcount), a tiny init for k8s called Pebble, a CharmHub and an operator framework. Examples: Charmed magma (≈50 microservices) and Kubeflow (≈35 microservices); a Terraform provider and a relations language enable cross-cloud composition.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 1:00Open Source
- 2:31Support
- 2:56Is this already solved
- 4:16Why open source
- 5:35What is Juju
- 5:56Deploying
- 7:26Software Lifecycle
- 8:00Flexibility
- 9:35Postgres
- 10:23Connectivity
- 12:26Application Catalog
- 13:25Building Charms
- 14:38GitHub
- 15:40Community
- 16:20Roadmap
- 16:48Questions
- 17:12Machine Charms
related talks
11mInterview
42mPythonic deployment of (Python) applications
39mTo the Clouds: Why you should deploy to the cloud even if you don't want to
23mDeploying OpenSearch Solutions on Hybrid Multi-Cloud Environments
27mBroader Adoption of FINOS Projects, Case Studies - Charming Legend and Waltz
41mPragmatic DevOps
16mUdi Nachmany | Google Next 2017
21mHow Open Source can Address Enterprise Software Ops Challenges?