White Papers

Understanding OPNFV

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

Contents of this Issue

Navigation

Page 51 of 144

Understanding OPNFV 51 OPNFV is a "Midstream" Project Software development draws on analogies from rivers (which is very interesting given that OPNFV projects are also named after rivers) by using terms such as "upstream", "downstream", and so on. Upstream describes the code base from which a downstream code base is forked. In the context of open source, upstream describes the master repository that all contributors work on. Downstream refers to forks made to create releases and to apply specific features or bug fixes. Upstream and Downstream Open Source OPNFV is a unique project because it works both upstream and downstream. The integration and testing pillars are a downstream activity, while new feature development, on the other hand, is an upstream activity. For this reason, OPNFV may also be called a "midstream" project. Benefits of Open Source Since OPNFV is an open source project, a brief refresher on the benefits of open source might be in order. Open Source Supplements Open Standards The vehicle to gain interoperability, until recently, had been open standards. Open standards were a way for end users to, increase the set of possible vendors to avoid vendor lock-in and foster innovation. However, as Sterling Perrin makes the case eloquently in a Heavy Reading 2016 report, standards are unable to keep up with the pace of current innovation. Standards also

Articles in this issue

Links on this page

view archives of White Papers - Understanding OPNFV