White Papers

Understanding OPNFV

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

Contents of this Issue

Navigation

Page 128 of 144

Understanding OPNFV 128 ● VNF onboarding platform: There is no easy way to compare benchmarks across VNFs since the underlying NFVI, SDN controller and VIM platform is not consistent across vendors. By using an OPNFV scenario, end users can standardize on a consistent environment against which different VNFs can be tested, characterized and benchmarked. Moreover, users can utilize Yardstick and other OPNFV performance testing projects to validate platform performance in-house. This results in both a time- to-market reduction and an improved technology stack resulting a higher project return- on-investment (ROI) for the end user. ● Best-in-class components: One of the major benefits of open source software, as we discussed in Chapter 3, is to be able to pick and choose best-in-class components aligned with specific use cases. OPNFV deliberately provides multiple choices at different layers of the NFV stack enabling this selection; this in turn results in a greater project ROI by increasing the value of the stack and freeing up valuable developer resources for other activities. ● No vendor lock-in: Another major benefit of open source software is the ability to eliminate vendor lock-in. Assuming the market is large enough, there are bound to be multiple vendors; and this drives down cost and makes it possible for users to switch vendors. We are by no means minimizing the effort of switching vendors, but it is significantly smaller than what would be required when switching across proprietary technologies. This results in a clear total-cost-of-ownership (TCO) reduction. ● Product that solves real problems: Rather than communicating with a proprietary vendor's engineering team through an army of gatekeepers such as account executives, systems engineers, product managers, systems architects, field CTOs, and so on, in the OPNFV community, users can work side-by-side with engineers from a vendor to ensure that features they care about are included in the product. Or users can contribute features themselves. This results in an improved project ROI for end users. Intangible Benefits It would be myopic to consider OPNFV as just technology. By getting involved with the OPNFV community, telecom operators can gain insights into all aspects of NFV transformation to speed up their journey. Specifically, let's revisit the four pillars of NFV transformation discussed in Chapter 2, and evaluate how OPNFV helps with each one. Impact to Organizational Structure The 45+ project teams in OPNFV are small groups that consist of a PTL (project technical lead),

Articles in this issue

view archives of White Papers - Understanding OPNFV