The Big Decision when Adopting Openstack as a Private Cloud
summary
Advice: expect three hard constraints when deploying OpenStack on-premise—long-term scalability and hardware flexibility, the operational complexity of designing and maintaining many OpenStack projects and deployment tools, and significant upfront capital expenditure. Mentions 22 releases (Victoria) and that OpenStack issues releases every 6 months, so upgrades become regular work; plan monitoring, upgrade cadence, and whether to support VMs, bare metal, or Kubernetes. Suggests a hosted private cloud converts capex to opex as an alternative.
AI-written summary · about
chapters (9)
- 0:00Start
- 2:45Developing a Long-Term Sustainable Strategy
- 5:35Hardware Flexibility
- 7:14Designing and Architecting
- 8:32Openstack Distribution
- 10:23Openstack Upgrades
- 11:13Everyday Management
- 12:19Capital Expenditure
- 13:01Hosted Private Clouds
related talks
29mOpenStack public clouds: 7 reasons to become a local cloud service provider
29mShould We Invest in New Servers When Building a New Cloud?
23mOpen Matters: HP & OpenStack
20mAre the days of on-premise servers over?
31mOn-Prem is the new Black
38mHow OpenStack became boring (and successful)
49mIntroduction to OpenStack
28mWhat is OpenStack and what services do I need?