OpenStack and Brocade - Ken Ross, Dir. Prod. Mgmt, NMS, Brocade - OpenStackSV 2014
•Download as PPTX, PDF•
1 like•3,262 views
Lightning Talk by Ken Ross, Director Product Management, NMS & Orchestration, Brocade, at OpenStack Silicon Valley (OpenStackSV) - 9/16/14
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (20)
More from Mirantis
More from Mirantis (14)
Recently uploaded
Recently uploaded (20)
OpenStack and Brocade - Ken Ross, Dir. Prod. Mgmt, NMS, Brocade - OpenStackSV 2014
- 1. Ken Ross Director Product Management, NMS & Orchestration Brocade Lightning Talk CONFERENCE ORGANIZER SEPTEMBER 2014
- 2. SEPTEMBER 2014 OpenStack Contributions • Cinder : SAN FC • Tacker : Services VM • Multi-tenant DC-DC via MPLS • NFV ETSI POCs inc. scheduling • FWaaS, VPNaaS
- 3. SEPTEMBER 2014 OpenStack Challenges • Neutron Maturity • Evolving functionality • Virtual Networking - Industry Transition • SDN & Open Daylight • Delivering on Agility & Managing Success • Balancing community innovation and reliability
- 4. Thank you For your contributions CONFERENCE ORGANIZER SEPTEMBER 2014
Editor's Notes
- I’d like to talk briefly about Brocade’s experience getting involved with OpenStack and some of the challenges we see going forwards. Brocade has been tracking and investing in OpenStack for over 3 years now and one of the main lessons for Brocade in supporting OpenStack has been to both internalize the market importance of open source, and to recognize the cultural importance of getting actively involved & contributing to the community - rather than just developing product pluggins. As an organization we’ve started evolving to support both SW networking (VNFs) as well as HW product lines and through that transition we started by contributing plug-ins to ensure the support desired by existing customers, and are now contributing to advancing the functionality of OpenStack – you can see some examples here – Working through that transition has involved skillset and toolset transitions (as basic as cli to Linux), agile process adoption and cultural recognition of the importance of open source – however the promises of extensibility, agile delivery and community involvement have their challenges…………
- We’ve seen phenomenal adoption of OpenStack in the designs and architectures of the future – from cloud management to SDS to NFV – that success comes with some growing pains :- Firstly, the ability to mature sufficiently rapidly on the Neutron side – there is a challenge both in terms of meeting the needs of early adopter customers & the resources required to get a contribution successfully included in an OpenStack release in a reasonable timeframe. Issues of stability, changing model definitions and breadth of contributions coming in mean that contributions do not necessarily get accepted. Developers and the vendor community are trying to grow the value of the OpenStack ecosystem but there is a lot of frustration with the bottlenecks around the review system. We are seeing a build up of desired enhancements and pluggins that are now deployable, but not available upstream. We’re asking our distribution partners to certify them “out of band”. In general there is a perception that OpenStack is not ready for prime time and commercial viability – flexibility in supporting adoption of the commercial distributions will help scale adoption, and in turn benefit the community. As we work through how to scale and how to address some of the inertia we’re seeing, we’re beefing up the resources and skill set transitions, and watching closely how the relationship between Neutron and OpenDayLight will evolve. A number of developers are heavily involved in both, and specifically working on the interface between the two projects. It would be good to have a broader industry understanding about the relationship and their respective roles going forwards. Of course the very characteristics of a large community that contribute to the inertia, do help the longer term open source benefits of innovation that stem from from community variation, and reliability (ref. dmm blog) In the words of Forest Gump, “that’s all I have to say about that.”