White Papers

Understanding OPNFV

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

Contents of this Issue


Page 53 of 144

Understanding OPNFV 53 However, for a subset of use cases such as vIMS, a public cloud may be an option. Also, parts of the NFV stack such as MANO software could be hosted in public clouds. The following could be alternatives to OPNFV: ● Proprietary virtualization solutions: Technologies such as vSphere ESXi, proprietary MANO or SDN controllers are potential alternatives to the OPNFV stack. So Why Should I Care Again? As we saw in Chapter 2, NFV transformation is more about process, organization structure, and skill set acquisition than about technology. OPNFV is an unparalleled community with deep exposure to these aspects in addition to technology. As the remaining part of the book will show, Model driven architecture, DevOps and cloud native software are baked into the DNA of OPNFV. Participation in OPNFV could save you multiple years of false starts, and tens if not hundreds of millions of dollars in wasted expenditure. Form a purely technical point of view, you may still be thinking that if OPNFV is not a standard open source software project with a ready-to-use single distribution that you can use, why should you spend time on it? Well, if you are looking to deploy NFV across telco or enterprise networks using open source projects, consideration of OPNFV is critical. OPNFV, in a nutshell: ● Promotes integration and interoperability: Open source projects are unlikely to work together out-of-the-box. OPNFV ensures combinations of different projects work together. The integration work is not trivial. Even if a user or vendor chooses not to use OPNFV artifacts, the integration work will cut down internal R&D work significantly; and those resources can be redirected to higher value activities. ● Drives requirements: OPNFV drives key NFV-centric features and code into relevant upstream projects. In short, OPNFV is like a take-and-bake pizza. It's not completely cooked and ready to eat, but it has taken care of numerous labor intensive steps that reduce your time to eating, or in this case, time to NFV in production! See Chapter 10 for a deeper discussion on the benefits of OPNFV. {Create-Compose-Deploy-Test}.Iterate To summarize, the goal of OPNFV is to create new features, integrate a variety of upstream open source projects to compose NVF stack(s), deploy and test them. This entire cycle gets repeated over and over again, triggered by any upstream component change. In subsequent chapters, we will look at each of these four stages (create, compose, deploy, test) in more detail.

Articles in this issue

Links on this page

view archives of White Papers - Understanding OPNFV