Open Source Infrastructure: Another Path of Growth for Open Source
summary
Gluster moves infrastructure into reproducible automation: infrastructure as code with code review and planned downtime windows, starting by converted one set of jobs and iterating from there. Access control tightens gradually—admin-only two‑factor authentication first, not a global surprise—and roadmaps plus published priorities steer requests. The claim is concrete: small, testable infra changes reduce firefights; the team fixes jarred issues, adds automated testing and release management, and measures success by fewer emergency rollbacks and clearer contributor paths.
AI-written summary · about
chapters (16)
- 0:00Intro
- 2:55Release cycles
- 3:25Shipping software
- 4:30Locks
- 5:11Infrastructure as Code
- 5:48DevOps
- 6:14Timelines
- 7:31Mistakes
- 9:58Roadmaps
- 10:11Pain Points
- 10:41My Mistakes
- 11:40Shave and Yak
- 12:27The Road Map
- 12:48Conclusion
- 13:42What has done
- 15:51Question
related talks
43mThe Open Sourcing of Infrastructure
09mWhy choose open infrastructure?
27mOpen Sourcing Your Infrastructure
36m4 Opens and the Open Infra Way
42mOpen Source in the Age of Cloud and Microservices
28mUnlocking Agility with Open Source: A Guide for Modern Businesses
15mLessons learned: Guidance on how to make open source development a success
32mMastering Enterprise Open Source for Cloud and Vendor Independence