The Open Sourcing of Infrastructure
summary
Argues that actually releasing infrastructure code lets other projects reproduce entire stacks: cites OpenStack CI and an open-sourced research lab that publishes hardware layouts, configs and puppet/juju artifacts so teams can deploy identical environments and fix bugs themselves. Describes tools used: OpenStack, Juju charms, Docker/Kubernetes and DC/OS on Mesosphere, plus Puppet/Chef. Notes failures that matter — S3 outage, vendor lock in, unclear pricing and missing postmortems — and shows community-published dashboards and configs that demonstrably work.
AI-written summary · about
chapters (19)
- 0:00Intro
- 0:55Background
- 2:30History of Infrastructure
- 2:52The World 15 Years Ago
- 3:11The Revolution
- 4:49Linux
- 5:48Linux Users Group
- 6:38Open Source
- 8:32Downtime
- 12:31Microsoft
- 13:11Aqua
- 14:01Configuration Management
- 16:01Security
- 20:59Problems
- 26:53Companies
- 27:54Services
- 28:42Private Cloud
- 30:59Open Source Projects
- 34:52Questions
related talks
27mOpen Sourcing Your Infrastructure
40mOpen Operations for Clouds and Services
09mWhy choose open infrastructure?
36m4 Opens and the Open Infra Way
17mOpen Source Infrastructure: Another Path of Growth for Open Source
25mLessons Learned from Cultivating Open Source Projects and Communities
42mOpen Source in the Age of Cloud and Microservices
53mKeynote - Embracing Openness as a Competitive Advantage