Open Sourcing Your Infrastructure
summary
Argues for releasing production configuration and reference implementations instead of abstract examples, citing open-sourcing most department infra while keeping passwords and GPG blobs private. Describes concrete artifacts to publish: salt ops repo, Chef and Packer manifests, Packer build configs, runbooks, Glue code that brings up RDS, Redis, nginx and app servers, and a secrets backend using HashiCorp Vault. Notes BSD 3-clause licensing and a continuum from single modules to full stacks.
AI-written summary · about
chapters (7)
- 0:00Start
- 1:39Jimmy Guerrero the Vp of Marketing from Signify
- 3:21Sponsors
- 3:51Tobias Mace
- 6:15Why Do You Want To Open-Source Your Infrastructure Code
- 11:44How Can You Get Started
- 15:13Overall Architecture Patterns
related talks
43mThe Open Sourcing of Infrastructure
42mOpen Source in the Age of Cloud and Microservices
32mMastering Enterprise Open Source for Cloud and Vendor Independence
04mThe role of open source in a company
32mBecome an Open Source Service
17mOpen Source Infrastructure: Another Path of Growth for Open Source
25mLessons Learned from Cultivating Open Source Projects and Communities
15mLessons learned: Guidance on how to make open source development a success
