White Papers

Understanding OPNFV

Issue link: https://read.uberflip.com/i/1344850

Contents of this Issue

Navigation

Page 47 of 144

Understanding OPNFV 47 3 IT'S A BIRD, IT'S A PLANE, IT'S OPNFV! Just as onlookers were mystified at the sight of Superman streaking through the sky, those trying to understand OPNFV through the lens of traditional open source projects might be confused by its somewhat non-traditional nature. Let's look at the driving factor for creating yet another open source project before exploring what OPNFV is. OPNFV Driving Factors The underlying assumption of OPNFV is that open source software and collaboration techniques are an attractive way to create parts of – if the not the entire – software stack defined by ETSI (see Chapter 1). As there is no shortage of open source networking projects to work with, this should be straightforward, correct? Actually, no! When applying these open source projects to a specific use case such as NFV, four interesting challenges arise: ● Influencing projects: Large open source projects have two idiosyncrasies when it comes to roadmap definition. First, there is no central product management or equivalent entity driving specific features. This decision-making happens in a much more distributed fashion. Second, these projects often target multiple use cases. So, it is a challenge to steer open source projects toward one specific use case such as NFV. ● Composing the stack: NFV requires software from multiple open source projects. No one project is going to own the responsibility of making sure that all these pieces of software are integrated and interoperate. Composing different flavors of stacks based on these upstream projects is especially difficult, as they approach problems from three distinct points of view: web-scale, network, and IT. The challenge is to blend the three

Articles in this issue

view archives of White Papers - Understanding OPNFV