Same Procedure as Every 4 Years - Cloud Foundry Stack Migration
summary
Migration from cflinuxfs3 (Ubuntu 18.04) to cflinuxfs4 (Ubuntu 22.04) is described end-to-end: cf-deployment integration rolls fs4 into releases (23.3 opt‑in, 27 full buildpack coverage, 28 default, 30 ships fs3 only opt‑in) and platform operators use the Cloud Controller API, buildpacks and opsfiles to restage apps. A central graceful migration tool is built to fetch packages, change stack, restage and health‑check, reverting on failure. At SAP scale (100K+ apps across ~30 landscapes) about 80% migrate with little customer impact; ~20% remain problematic.
AI-written summary · about
chapters (11)
- 0:00Introduction and speaker
- 1:05What is a stack in Cloud Foundry
- 2:08Stack versions and support status
- 3:11Default stack behavior and migration
- 4:15Timeline of stack migration process
- 6:46Platform operator perspective at SAP
- 8:36Central stack migration procedure
- 12:09Challenges and solutions in migration
- 15:42Ideas for improving stack migration
- 16:45Conclusion and dilemma of migration
- 17:26Q&A session
related talks
30mBanking on Cloud Foundry Platform: A Case Study of Digital Business Banking Applications
45mHow we rebuild a legacy monolithic platform at CERN and still sleep at night
42mBeyond CF Push - Managing Large Microservice Applications like a BOSH
27mBuilding Momentum Toward Cloud Foundry
15mKeynote: Who Wants to Win a Good AppTx?
30mMigrating a monolith to Cloud-Native and the stumbling blocks
38mThe Good, the Bad & the Ugly of Migrating Hundreds of Legacy Applications to Kubernetes
33mMigrating the Bluemix UI to a Microservices Architecture on CloudFoundry