Challenges of scaling a upstream Openstack Cloud
summary
Société Générale runs an upstream OpenStack private cloud with 18k VMs across 4 regions and ~450 compute hosts (≈350 in Paris), sees ~1,500 instance create/destroy ops per day, and grows control nodes from 3 to 12 in Paris to handle control-plane load. Major problems: massive VLAN/provider-network segmentation causing exploding security-group rules (~160k rules), Open vSwitch agent being single-threaded and failing with ~60–70 rules per port, and segments/subnet limits. Remedies: merged restart-rate patch, segment plugin patch under review, internal security-group and OVS patches planned for upstream.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 0:42Multicloud strategy
- 1:40Global deployment
- 3:05Storage
- 3:43People
- 9:23Security
- 12:33QA
related talks
18mAchieve a single Openstack deployment in multiple datacenter
30mOpenStack Works, so now what?
27mLessons Learned from a Large Scale OpenStack Deployment with Tripleo
19mHow open source contribution has increased work efficiency of a French bank ?
34mHeadline Panel: Global Enterprise IT Companies Supporting OpenStack
22mMoving a Large Workload from a Public Cloud to an OpenStack Private Cloud...
17mBuilding the Rackspace Open Cloud with XenServer and OpenStack
19m10 years of OpenStack at CERN (From 0 to 300k cores)
