White Papers

Understanding OPNFV

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

Contents of this Issue


Page 97 of 144

Understanding OPNFV 97 7 OPNFV AUTOMATED SOFTWARE DEPLOYMENT One of the main goals of OPNFV CI, as we saw in the previous chapter, is the continuous and automated testing. The testing process occurs in two steps: 1. The CI process deploys a set of upstream projects with specific configurations 2. The CI process runs automated test(s) against the deployed software In this chapter, we will cover the first step; we'll look at the second step in Chapter 8. What Are OPNFV Scenarios? An obvious question emerges: if the OPNFV project integrates multiple software projects for several layers, then what exactly is being tested? For example, you can't possibly test ODL, ONOS and OpenContrail all at once. Nor can you test OVS and FD.io at once. Also, there are numerous variations in configurations, such as high availability, DPDK, service function chaining (SFC), BGPVPN and so on, where choices have to be made. To solve this conundrum, OPNFV has come up with the concept of scenarios. Scenarios are a deployment of a set of components and their configuration

Articles in this issue

Links on this page

view archives of White Papers - Understanding OPNFV