Telecom IQ
Showing results for 
Search instead for 
Did you mean: 

OpenNFV Partner Corner: Openness is a means to an end. The end is a system that works.


Guest Author: Jeff Gowan, Senior Product Marketing Manager, Wind River


Wind River, an HPE OpenNFV partner, recently teamed up with TelecomTV and OPNFV to explore the question, “What does Open really mean for NFV?” Through a series of many conversations, multiple video interviews and a survey, we’ve compiled some insights to answer that weighing question. . For a sampling of interview answers from OPNFV Summit attendees take a look at this video

If you’d rather take a look at summary of the feedback, take a look at the survey results here:

 In the survey, we asked questions to attempt to understand what Service Providers are specifically asking for when they ask for an “open” solution. What we found is that the core requirement is not simply openness in itself, rather it is the perceived benefit resulting from openness. In this context “openness” implies a solution comprised of hardware/software elements that work together and are interoperable. Openness also implies there is no “vendor lock-in” which seems to be a huge concern for service providers. Another big concern for service providers is carrier grade availability and reliability, however at this point this benefit is neither implied nor expected from an open solution. At the end of the day, what is important is building a system that works. Openness is a means to that end.

In the survey, we asked 12 questions, including two open-ended write-in questions. The questions were intended to obtain a better understanding from the audience as to what is meant by open, and whether it varies depending on who you ask. For example, what happens if you strip out the noise being made by vendors vs what service providers actually want? We also wanted to understand if the requirements are different between a proof-of-concept (POC) and a commercial deployment.  


A couple of interesting tidbits from the report:

  • 32% of respondents are currently deploying an NFV solution
  • When defining an open solution for NFV, the emphasis is on fully open source licensed from an existing project with vendor support, and compatibility with de-facto standards.
  • 63% don’t expect to get all the reliability and availability they need from pure open source and most think deployable open source NFV is more than 2 years away.
  • Open solutions are seen as very important when considering avoiding vendor lock-in and interoperability, but less of a factor when considering differentiation
  • When service providers move from a POC to a commercial deployment, having code that is open is less important than actually ensuring interoperability, carrier grade availability and reliability

 To download and read the full report go here.


Visit us at our HPE OpenNFV website, and follow us on Twitter at @HPE_NFV and @HPE_CSP.

0 Kudos
About the Author


Nov 27 - 29
Madrid, Spain
HPE Discover 2018 Madrid
Learn about all things HPE Discover 2018 in Madrid, Spain, 27 - 29 November, 2018.
Read more
See posts for
HPE at 2018 Technology Events
Learn about the technology events where Hewlett Packard Enterprise will have a presence in 2018.
Read more
View all