White Papers

Understanding OPNFV

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

Contents of this Issue

Navigation

Page 50 of 144

Understanding OPNFV 50 OPNFV Release Timeline Arno Brahmaputra Colorado Danube Euphrates Sept. 2015 Mar. 2016 Sept. 2016 Apr. 2017 Est. Oct. 2017 Open Source Systems Integration Most people assume that an open source project is a group of programmers volunteering their time to develop a piece of code. However, open source projects don't need to focus on creating a piece of software. OPNFV is an integration project whose work involves testing, CI/ CD, documentation, and more. OPNFV is Systems Integration as an Open Community Effort What OPNFV is Not As described above, OPNFV integrates a variety of upstream open source projects, tests them, and then influences their roadmaps. However, OPNFV does not fork in order to enhance software projects or create new software functionality. That task is left to the various upstream projects from which OPNFV draws. That means that when OPNFV does enhance projects, it is done collaboratively in conjunction with the upstream community. Furthermore, even though OPNFV does extensive testing, it is not attempting to build a product. In other words, it does not prescribe any particular software combination for a particular application. That task is left to users and vendors. For these reasons, you don't necessarily download, install and run OPNFV artifacts like a traditional open source project. If you are a vendor, for the same reason, you are unlikely to have an "OPNFV distribution;" though you might have a commercial distribution of a software component that has been integrated or tested by OPNFV, or even an integrated product with several components from one of OPNFV's stacks.

Articles in this issue

view archives of White Papers - Understanding OPNFV