This is Not a Technology Problem: Leveraging Culture and Process to Make the Most...
summary
Argues that most Cloud Foundry pain comes from people and process not software, showing concrete fixes: replace manual installs with Concourse pipelines that automate upgrades, create sandboxes and promote the same inputs through preprod to production, run gamedays and a test suite that replays every past failure, use pairing/mobbing to raise bus factor, and staff a dedicated product-like platform team. Cites operational evidence: Cloud Foundry foundations stay online through infra failures (four hours) and the foundation ecosystem averages 137 releases a month.
AI-written summary · about
chapters (12)
- 0:00Introduction and background
- 1:46Cloud Foundry is difficult to operate
- 4:52Lack of automation and training
- 7:45Treating platform as a product
- 12:44Platform reliability myths
- 15:33Batch releases and fear of failure
- 16:59Sandbox environments and CD
- 18:05Documenting and testing incidents
- 20:13Digital transformation challenges
- 22:26Organizational commitment needed
- 25:11Role of product managers
- 27:51Q&A and closing remarks
related talks
32mThis is Not a Technology Problem: Leveraging Culture and Process to Make the Most...
19mKeynote: Confessions of a Cloud Foundry PaaS Product Owner: How to Create a Successful Devops Team
26mSkilling Up: How to Effectively Grow a Cloud Foundry Organization - Steve Greenberg, Resilient Scale
54mCloud Native Culture
32mOps in the Time of Serverless Containerized Webscale
44mNine Ways To Fail at Cloud Native
06mThe Gold Standard in Platform Engineering: Cloud Foundry :)
22mCrossing the CI/CD/DevOps Chasm - Miranda LeBlanc, Liberty Mutual