Bulk Application Migration Between Cloud Foundries
summary
Client gives 30 days to move roughly 1100 apps across three CF foundations into a new Genesis/BOSH greenfield. Process inventories apps, services, domains and certs, probes service connectivity with nmap/netcat, repeatedly runs a final blobstore sync and a PG dump with checksums, schedules downtime for single‑instance apps, stops job writers, loads databases, then issues BOSH start and watches Diego converge. Migration completes successfully within the change window.
AI-written summary · about
chapters (17)
- 0:00Intro
- 2:14Assumptions
- 4:11The big picture...
- 4:32Databases
- 5:27Largest applications
- 6:19Failing applications
- 6:37Service reachability
- 7:08Housekeeping
- 7:39Test & time data transfers
- 8:17Pre-sync blobstore
- 9:01Time the database dump
- 9:57Schedule your migration
- 11:30Final blobstore sync - our first step
- 11:52Old site: Dump database
- 12:25New site: Who is using the database?
- 13:39New site: Startup
- 14:10Watch apps converge
related talks
24mMigrating Large Scale CF Environments
29mThe Challenges of Taking Open Source Cloud Foundry to Production
25mMass migrations to the cloud
17mDeployments We Can Believe In
31mWinning in Production
16mDeployments We Can Believe In
24mCF-Motion: Live Migration of Cloud Foundry Applications and Data
25mDeploying Cloud Foundry with BBL, Bosh 2.0 and CF Deployment