White Papers

Understanding OPNFV

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

Contents of this Issue


Page 95 of 144

Understanding OPNFV 95 on whether to include or exclude specific projects based on maturity and readiness. As you might expect, the ultimate goal is to evolve to a continuous delivery approach where releases are available at a higher frequency and ultimately, the trunk is stable at any given point in time. Making CI/CD More Continuous The use of DevOps and CI is quite advanced in OPNFV; however, there's always more to do. One important aspect is security checking, where every commit will get checked for security violations using automated tooling. Under consideration are checks such as Lint and vulnerability scanner for source code files, the inclusion of binary objects, use of strings that might contain passwords, keys or hashes and missing licenses. When it comes to consuming upstream projects, the default practice is to use regular stable releases. The next step, already in place with certain projects, is to consume upstream projects on a more regular basis, even daily. Using this process, OPNFV can do two things i) provide feedback for each commit using health checks and ii) run daily and weekly tests on the latest code base. The OPNFV Cross Community CI initiative, or XCI, covers these newer processes initially for OpenStack, ODL, FD.io and ONAP. The benefits of XCI are faster access to the latest innovation and rapid feedback to the upstream community. CI/CD Today & in The Future These improvements are some of the more visible, but constant evolution is going on behind the scenes as well, in an attempt to be cleverer in the execution of tests, to improve the utilization of

Articles in this issue

Links on this page

view archives of White Papers - Understanding OPNFV