Downloaded 19 times
Uploaded byTesora
OpenStack Management at Hyperscale
The document discusses Verizon's OpenStack-based cloud platform and the challenges of managing it at a hyperscale level. Some key points discussed include defining Verizon's cloud platform to provide on-demand, self-service infrastructure to users; the difficulties of managing large and distributed cloud deployments at scale; and facilitating easy self-service for users while also providing operators visibility into utilization, capacity, and other metrics. The document also covers Verizon's use of OpenStack metering and APIs to track usage at scale and provide reporting to stakeholders.
More Related Content
![Introduction [compatibility mode]](https://cdn.slidesharecdn.com/ss_thumbnails/introductioncompatibilitymode-120611142750-phpapp02-thumbnail.jpg?width=640&height=640&fit=bounds)
Similar to OpenStack Management at Hyperscale
OpenStack Management at Hyperscale
- 1. OpenStack Management at Hyperscale AndrewHendrickson, Verizon Sanjay Mishra, Talligent August 24, 2016
- 2. • Andrew Hendrickson,Verizon • Sanjay Mishra, Talligent
- 3. Topics • The VerizonCloud Platform • Hyperscale • Why do this? • Finding focus • The Orchestration issue • Challenges • Managing hyperscale for cloud • Facilitating self service 3
- 4.
- 5. 5 Define • large scalecloud with built with OpenStack • defined by services – not tenants • give users ability to quickly deploy and support applications • a common interface for infrastructure • on-demand // self service
- 6. 6 Hyperscale • it islarge (relatively speaking) • lots of instances • lots of projects • lots of users • distributed • elastic • easy to use • predictable • tells you the truth
- 7. 7 Why VCP? • Thenetwork is the most valuable asset • Get new features to customers faster • Improve agility for developers and suppliers • Reduced costs – upstream and downstream • Distributed • Disposable • Dependable
- 8.
- 9.
- 10. 10 Challenges • hype-rscale • repeatablebuild – break • community maturity • resiliency in carrier grade • user experience • demonstrating Value • operations ≠ operations • organization
- 11. 11 Hands Free • Versioncontrol everything • Machine readable files • No physical configuration • Bare metal • Servers • Network gear • The stack • Web style serialization/delivery • Declarative is fun • Version control everything • Bots
- 12. 12 Managing Hyperscale • Infrastructure • Pre-requisites •Storage • Stack Build • Monitoring • Security • Upgrade // patch • Products • Data Retention • Identity • Metering • Self service experience
- 13.
- 14. Self-service requirements •Instant •Real-time visibility •Easy- Simple •Distributed •Fun 14
- 15.
- 16. Stakeholders • Operators • Projectowners • LOB managers • Executives • Utilization • Capacity • History • Forecasts • Service adoption • Budget performance • Tenant/customer size KPIs
- 17. OpenStack Metering/Integration • OpenStackService APIs • A note about Ceilometer • Resolution • Creating a historical record • Metering at scale • Reporting and Openbook APIs 17
- 18. Results To Date/LessonsLearned • User experience is key! • Keystone v3/Authentication • Tracking DBaaS/NFV • SLAs • Organizational/User buy-in 18
- 20. Summary • The VerizonCloud Platform • Hyperscale • Why do this? • Finding focus • The Orchestration issue • Challenges • Managing hyperscale for cloud • Facilitating self service 20
- 21.
Editor's Notes
- #15 Instant Provisioning Real-time Visibility – Cost and Consumption Simplified Service Request Distributed (not top down ticketing request process)