OpenStack Works, so now what?
summary
OpenStack already runs real scale: 10–20k VMs a day across three (soon six) public clouds, about 1.7 million test jobs in six months and ~18 TB of logs in that period, all using only OpenStack APIs. A daemon called nodepool keeps a ready pool of single-use nodes, a library called shade encodes hundreds of cloud idiosyncrasies, and new Ansible modules and os-client-config hide provider quirks. The system works but the talk argues for standardizing those divergences to make simple things simpler.
AI-written summary · about
chapters (26)
- 0:00Introduction
- 1:08What is Meta
- 1:50OpenStack
- 2:50Agenda
- 3:36What is OpenStack
- 5:10The Internet
- 6:45Node Pool Activity
- 8:00OpenZac Infosystems
- 8:45Gated Commits
- 10:55Diagrams
- 12:50Garrett
- 13:28Single VM
- 17:15Multicloud
- 18:25Graphs
- 19:25Whats next
- 20:30Get a base image
- 21:35Download prebuilt images
- 22:25Rackspace
- 23:35Image API
- 24:30External Routing
- 25:35Old Bug
- 25:55Config Library
- 26:35Client Config
- 26:50Shade
- 27:10Python API
- 28:10Summary
related talks
18mOpenStack Playing for an Open World
23mOpen Matters: HP & OpenStack
49mIntroduction to OpenStack
18mWhat is OpenStack?
38mHow OpenStack became boring (and successful)
54mOpenStack Development: The Infrastructure Behind the Infrastructure
18mChallenges of scaling a upstream Openstack Cloud
19m10 years of OpenStack at CERN (From 0 to 300k cores)