Taking Cloud to Extremes: Scaled-Down, Highly-Available, and Mission-Critical
summary
Cloud Foundry on OpenStack gets a practical plan: etcd 3 instances and at least one Gorouter per AZ, blobstore moved to OpenStack Swift, and sensitive components like CC/UADB backed by bosh resurrection ~2–4 min or external MySQL Galera; bosh director VM recreation runs ~25 minutes in tests. Cassandra runs on a 6-node cluster RF=3 using cassandra-stress for 5-minute benchmarks and can meet a 10,000 ops/s goal with low latency in that setup. Deliverables include a Cassandra service broker and web console deployed on CF.
AI-written summary · about
chapters (10)
- 0:00Cloud Foundry Planning
- 1:51Cloud Foundry HA Deployment Issues
- 3:40BOSH Director Recovery
- 5:17Blob Storage in OpenStack Swift
- 6:15BOSH Resurrection
- 8:27Cassandra in OpenStack Caph
- 9:41Cassandra in OpenStack Cape Pros and cons
- 11:43Testing Cassandra in OpenStack Ceph
- 14:51Cassandra Recommendations
- 16:44Alloros's Contributions to Cloud Foundry
related talks
48mCloud Foundry - your PaaS on OpenStack
29mLessons Learnt Operating Multiple Cloud Foundry on OpenStack Deployments
30mLiberate Your Cloud Foundry Installation From Being Constrained to a Single Cloud
23mCloud Foundry and OpenStack
40mThe Rocket Science of Deploying Cloud Foundry in Multi-Cloud Environments
33mNot Only for Giants: The Minimal Reasonable Size of a Cloud Foundry Implementation
21mA Roadmap to Active Multi Cloud
31mA Developer’s Perspective on Cloud Foundry Operations: One Month in the Trenches