White Papers

Understanding OPNFV

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

Contents of this Issue

Navigation

Page 87 of 144

Understanding OPNFV 87 6 OPNFV CONTINUOUS INTEGRATION As we saw in Chapter 4, OPNFV integrates a number of upstream projects. To achieve this integration in an automated manner, OPNFV has created a Continuous Integration (CI) pipeline supported by three infrastructure (infra) projects 3 : RelEng, Pharos and Octopus. These three projects are critical for the success of the OPNFV project. We will review these projects and then see how they are used for integration and release processes. Chapters 7 and 8 will discuss how the CI pipeline is used for deployment and testing. OPNFV RelEng: Release Engineering The RelEng project defines and supports the software infrastructure required to make OPNFV a success. It collects requirements from various OPNFV projects, sets up all the tools, software automation jobs, scripts, and so on – everything needed to automate integration, deployment and testing. The project also provides guidance and support to other projects on the best practices around using the software infrastructure. The main tools provided by the RelEng along with Linux Foundation infrastructure team are as follows: ● Collaboration: JIRA/Confluence ● Source code management and code review: Git, Gerrit and Github ● CI/software automation: Jenkins ● Artifact repository: Google cloud storage and Docker hub 3 These projects are used by deployment and testing projects as well

Articles in this issue

view archives of White Papers - Understanding OPNFV