White Papers

Understanding OPNFV

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

Contents of this Issue


Page 113 of 144

Understanding OPNFV 113 vendor lockin. This is easier said than done. How might a user verify that a vendor's distribution is consistent with the original project, and that some aspects haven't been (inadvertently) changed? In the case of OPNFV, it's even harder, because there's isn't one single distribution to deal with. Instead, there are numerous scenarios, any one of which could be considered as the basis of a distribution. Dovetail solves this problem by providing compliance tests. By running these tests, which heavily leverage Functest and Yardstick, Dovetail forms the foundation of the Compliance Verification Program (CVP) for commercial products. The goals of the CVP is to help build the market for OPNFV-based infrastructure and applications designed to run on that infrastructure, reduce adoption risks for end-users, decrease testing costs and enhance interoperability. Dashboards There are many dashboards to interact with and to visualize test results. We can classify them by: Scenario status reporting, complex results display (Grafana) or API interaction (Swagger). For the Danube release, they can be accessed from a central portal. Scenario reporting results are available for Functest, Yardstick, Storperf and VSPERF. For Functest there's also reporting on the vIMS VNF testing. For example: Functest Dashboard Yardstick results can be visualized through a Grafana dashboard (creds opnfv/opnfv). Any test

Articles in this issue

Links on this page

view archives of White Papers - Understanding OPNFV