White Papers

Understanding OPNFV

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

Contents of this Issue


Page 110 of 144

Understanding OPNFV 110 One additional point: each individual upstream contribution project is responsible for developing its own tests, and global tests that are not under the purview of a given project are covered by the activities of test projects. Let's take a deeper look into those test projects. Test projects OPNFV test projects are organized by scope. At the top level, there are functional tests (Functest), followed by performance tests (Yardstick along with a number of sub-projects) and OPNFV compliance tests (Dovetail). Functest The Functest project deals with the tooling and actual test cases around validation and functional testing of various OPNFV scenarios. The current focus is around VIM + NFVI functionality. The baseline is to use test cases from various individual upstream projects, such as Tempest (functional) and Rally (scale) for OpenStack, the Robot framework for ODL, and the Teston framework for ONOS. There are four reasons to repeat these upstream tests in Functest: 1) it tests projects together to ensure end-to-end interoperability, 2) it adds functional tests for the numerous OPNFV upstream contribution projects (the tests are also contributed back to the upstream projects), 3) it adds a number of end-to-end test cases, and probably the most important, 4) it incorporates open source VNFs, such as Clearwater vIMS, along with MANO projects to generate real-life test conditions on the underlying VIM + NFVI layers. Yardstick Yardstick is all about performance testing and is based on ETSI reference test suites. After surveying a large number of NFV workloads, the Yardstick project has broken down overall requirements into a set of performance vectors to quantify compute, network and storage aspects of NFVI. The project develops the test framework and test cases for each performance vector, and some test cases can get quite complex where Yardstick needs to run tests in parallel, inject faults, and test multiple topologies. Yardstick is extensible via a plugin architecture. It exposes and consumes APIs from specific performance testing sub-projects such as VSPERF (vSwitch), Cperf (SDN controller), Storperf (storage), Qtip (Benchmarking as a service) and Bottlenecks (bottleneck detection). Yardstick also includes traffic generation tools, as well as a Network Service benchmarking

Articles in this issue

Links on this page

view archives of White Papers - Understanding OPNFV