Managed CF-as-a-Service: An Operator's Cookbook
summary
Managed CF-as-a-Service runs cf-deployment on BOSH across three AZs, serving ~16,000 VMs with a three‑person DevOps team; pipelines use Concourse, mirrored artifacts on internal S3, and a cloud releases metadata repo to cut, test and promote immutable releases. Operators build self-contained BOSH releases (service broker, task runner, BBR, backup manager) co‑located for simplicity, favor single‑instance Postgres over Galera where HA adds fragility, and automate backups, testing and reproducible deployments so upgrades succeed with minimal manual intervention.
AI-written summary · about
chapters (10)
- 0:00Intro
- 1:43SWISSCOM APPCLOUD
- 4:52CENTRALIZED SERVICES (now - future)
- 6:14SELF-CONTAINED BOSH-DEPLOYMENTS
- 11:25RELEASE MANAGEMENT
- 16:48FROM A RELEASE TO A DEPLOYMENT
- 17:50DEPLOYMENT STRATEGIES
- 21:01HOW TO (NOT) PIPELINE
- 25:24TESTING-STRATEGIES
- 26:50MOST FREQUENTLY ASKED QUESTIONS
related talks
17mDeployments We Can Believe In
28mHow to Deploy CF and Other Bosh Releases on Bare-Metal Environment
42mBeyond CF Push - Managing Large Microservice Applications like a BOSH
32mIntroducing bosh-workspace: how we deploy all things BOSH
08mA Year with CF and BOSH
25mDeploying Cloud Foundry with BBL, Bosh 2.0 and CF Deployment
23mDeploying Cloud Foundry with BBL, BOSH 2.0 and CF-Deployment
29mCloud Foundry Growing Pains: Lessons Learned Keeping the Largest CF Environment Alive and Kicking