Migrating Large Scale CF Environments
summary
Large-scale Cloud Foundry migrations connect a Source and Target CF and run migration logic that reads Cloud Controller objects, maps names to new GUIDs, recreates spaces/orgs and service instances idempotently, and iterates until 80–95% pre-seeded; data services require per-broker backup/restore or replication (example: Postgres streaming replication option) and service-binding translation; certificates and domains must be reissued; final sync and DNS cutover take final cutover a few hours and teams report success after dozens of runs.
AI-written summary · about
chapters (7)
- 0:00Introduction to migration
- 1:47Migration scenarios and patterns
- 7:26Handling domains and certificates
- 10:15Iterative migration approach
- 12:44Dealing with data services
- 20:11Migration day and cutover
- 22:16Automation and project experience
related talks
16mBulk Application Migration Between Cloud Foundries
24mCF-Motion: Live Migration of Cloud Foundry Applications and Data
23mYour Data Center will Implode in 30 days, a Success Story
29mThe Challenges of Taking Open Source Cloud Foundry to Production
25mMass migrations to the cloud
31mPut Your Money Where Your CF Is
29mCloud Foundry Growing Pains: Lessons Learned Keeping the Largest CF Environment Alive and Kicking
20mAdvancing the Future of Cloud Foundry