Liberate Your Cloud Foundry Installation From Being Constrained to a Single Cloud
summary
Swisscom describes a working approach that runs one Cloud Foundry platform across multiple autonomous OpenStack stacks by extending BOSH to a multi-CPI BOSH so a single director deploys into distinct availability zones backed by different clouds. State services stay highly available via Galera and Consul/etcd, object storage uses S3 across four locations, and routing shifts traffic at the access layer. The implementation is running internally, pending official BOSH merge, and exposes latency, raft and placement as the main operational unknowns.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 1:52Swisscom
- 3:17Cloud is always on
- 4:57Business requirements
- 7:18Approach
- 12:04Deployment
- 20:25MultiCloud Deployment
related talks
40mThe Rocket Science of Deploying Cloud Foundry in Multi-Cloud Environments
28mManaging Multiple Clouds with a Single BOSH Deployment
21mA Roadmap to Active Multi Cloud
48mCloud Foundry - your PaaS on OpenStack
20mTaking Cloud to Extremes: Scaled-Down, Highly-Available, and Mission-Critical
29mSetting up a Multi-Cloud, Enterprise-Grade Cloud Foundry Installation: Bridging Infrastructure
32mExtending Cloud Foundry at Scale - Addressing the...
23mCloud Foundry and OpenStack