1 / 21

OpenStack Summit Hong Kong 2013: Community Contributions and Future Developments

Explore key highlights from the OpenStack Summit in Hong Kong, including local use cases, Ceilometer project updates, Neutron enhancements, and future plans for API improvements and feature expansions.

chavezt
Download Presentation

OpenStack Summit Hong Kong 2013: Community Contributions and Future Developments

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. OpenStack Summit Feedback • 5-8 November 2013 Hong Kong • Gergely Szalay • gergely.szalay@gmx.co.uk

  2. OpenStack Summit Hong Kong • Location: first summit outside US • 3000+ attendees • Top contribution: Beijing, Shanghai in Top10 • Local community

  3. Use Cases

  4. iQiyi.com • Chinese YouTube clone • 8 million transcodes • OpenStack powered backend, searches

  5. Quihoo 360 • Top3 ISP, 2nd most popular search engine,Nr1 Antivirus • 20 datacenter • 4000 instances

  6. CTrip • biggest travel and booking site • 20k members/day • 200k calls/day • currently 1000 VDIs • 13000 planned in 2014

  7. CEILOMETER

  8. Ceilometer / TELEMETRY • Official name now "OpenStack Telemetry" • Project objective: collect measurement data for monitoring and measuring • across all components • user-oriented feature • effort since Grizzly release

  9. Ceilometer project • track usage data: usage of instances • monitor performance: analyse resource consumption • metering demand for further resources • API contact for external systems (i.e. billing)

  10. Ceilometer architecture

  11. Ceilometer Workflow • Collect from OpenStack components • Transform if necessary • Publish meters (external or internal) • Store meters • Aggregate samples

  12. Billing Based On Ceilometer • Metering • Rating (transform usage data) • Billing

  13. Alarming • Set of rules or set of matching meters trigger specific action • Example1: • Heat auto-scaling based on usage data collected by Ceilometer • pre-defined CPU % utilization reached - trigger starting a new instance • Example2: • trigger alarms based on application centric data (i.e. object storage)

  14. New in Havana • API improvements (v2) • new storage backends • tighter integration with Nova

  15. Limitations • API limitation • choice of database backend (currently MongoDB) • storage of meters (keep everything or discard)

  16. Future - Icehouse release • further API improvements (v3): complex filtering and query, bulk requests • expand metering coverage • monitor baremetal • support for hardware polling • allow time constrained alarms • distributed polling • events storage (allows double entry accounting, auditability)

  17. NEUTRON

  18. New IN HAVANA • Load Balancer as a Service (LBaaS) revised- updated API, HAProxy supported • Firewall as a Service (FWaaS)- firewall rules, firewall policies • VPN as a Service (VPNaaS)- site-to-site IPSec VPN connections now supported

  19. Future improvements: Icehouse • multiple VIPs per pool • vendor API extension (vendor specific features) • Heat and Ceilometer integration

  20. THANK YOU!

More Related