The Challenges of Taking Open Source Cloud Foundry to Production
summary
Open source Cloud Foundry reaches production after a six month migration of 900 app instances across two foundations with 200 engineers and a six‑person platform team, requiring hands‑on work with cf-deployment, BOSH and custom ops files, a migration proxy implemented as a route service, compiling buildpacks, LDAP integration, and Concourse pipelines for deploy, smoke tests and backups. Monitoring, logging, restore procedures and patching (learn Go, build BOSH releases) turn out to be the ongoing operational costs.
AI-written summary · about
chapters (18)
- 0:00Fabian Keller
- 1:09Why self-hosting at all?
- 2:11The positions
- 4:04The Case
- 4:42The 4 Phases
- 7:59So what's the difference?
- 9:07BOSH BOSH BOSH
- 10:32Tailoring the Deployment
- 15:10Migrating to Another Foundation
- 17:23Upskilling
- 19:30Risk Management
- 21:06Buildpacks
- 23:22Upgrade Automation Roadmap
- 24:03Support
- 24:51Bug Fixing & Patching
- 26:23Failure Happens
- 27:53Cloud Foundry Operators Guide
- 28:29Retrospective
related talks
31mWinning in Production
17mDeployments We Can Believe In
50mCracks in the Foundation: Operating Cloud Foundry...
31mA Developer’s Perspective on Cloud Foundry Operations: One Month in the Trenches
31mPut Your Money Where Your CF Is
16mDeployments We Can Believe In
19mKeynote: Confessions of a Cloud Foundry PaaS Product Owner: How to Create a Successful Devops Team
29mLessons Learnt Operating Multiple Cloud Foundry on OpenStack Deployments