Lessons Learnt Operating Multiple Cloud Foundry on OpenStack Deployments
summary
Shows concrete operational recipes: automated Blue Box OpenStack + Cloud Foundry deployments using BOSH with a bespoke OpenStack CPI, an Ansible wrapper called Ursula (Ansible wrapper), Rally for validation and the OpenStack validator to preflight APIs, plus the fog gem to auto-generate manifests. Recommends custom flavors and gives a starting size (≈32 cores, ~700 GB RAM, ~6 TB disk, ~1.5 TB persistent → ~1 TB app memory) and a rule of thumb that each extra ~32 Diego VMs adds ~1 TB. The automation works and enables in-place OpenStack upgrades.
AI-written summary · about
chapters (19)
- 0:00Intro
- 0:40OpenStack Core Services
- 2:46Problems we faced
- 5:12Problems Community Faces: Survey Results
- 6:22Standardize around OpenStack Provider e.g. IBM Blue Box
- 8:07Bluemix : Architecture
- 8:31Can Cloud Foundry run on your OpenStack?
- 9:34Cloud Foundry Sample Sizing
- 10:35Cloud Foundry Capacity and Scalability
- 12:45Optimize OpenStack
- 15:05Optimize Cloud Foundry / BOSH
- 17:09Optimize Security and Network
- 18:40Account for customer boundary firewall or proxy
- 20:48Optimize Capacity
- 22:16Account for shared OpenStack Usage
- 23:15Update/Upgrade OpenStack
- 25:34IBM Blue Box OpenStack Install Automation
- 25:49Cloud Foundry on OpenStack deployment Automation
- 27:42Cloud Foundry on OpenStack - Great
related talks
23mCloud Foundry and OpenStack
48mCloud Foundry - your PaaS on OpenStack
20mTaking Cloud to Extremes: Scaled-Down, Highly-Available, and Mission-Critical
24mGulliver’s Travels In Cloud Foundry
29mThe Challenges of Taking Open Source Cloud Foundry to Production
25mCloud Foundry in Simple Terms: A Beginner's Journey
49mAutomation in Deployment on Hybrid Hosting and Private Cloud Environments
25mThe Essential Getting Started Guide to Cloud Foundry