Compliance Verification Program (CVP)

The CVP is a program initiated by the OPNFV Board of Directors with the following key objectives:

• • Help build the market for
    • OPNFV-based infrastructure
    • applications designed to run on that infrastructure
  • Reduce adoption risks for end-users
  • Decrease testing costs by verifying hardware and software platform interfaces and components
  • Enhance interoperabilit

Dovetail is the project that delivers all the open source software toolchain, documentation, and test suite for CVP. The Certification and Compliance committee (C&C committee) serves as the program's administrator on behalf the OPNFV Board.

More details of CVP can be found in the CVP document.

System Under Test (SUT)

The System Under Test (SUT) are products from vendors, not OPNFV release artifacts themselves. OPNFV development tooling, such as CI/CD, is also not part of the SUT. The vendors can bring up the SUT to a pre-Dovetail-test state in any way they choose. Dovetail will provide documentation to help the testers to prepare and configure the SUT.

In the current CVP version (Danube release time of Dovetail), the SUT consists of NFVI software, VIM software, and necessary hardware in one System Under Test. The hardware should follow Pharos guidelines (but generalized in the Dovetail documentation to remove specifics tied to ). Vendors can use their own hardware, or third party or white box hardware to be tested as a whole. And if the combined whole passes the test suite, the CVP label applies to the software.
The Danube cycle does not plan to test hardware-only systems.

• Test Suite

• CVP Compliance Test Suite

• Experimental Test Suite

• Test Area

• Test Case

• CVP server

• CVP (or Dovetail) client

• CVP User's Guide

• Test Area review worksheet document

Since dovetail project differ from those testing projects, such as (FUNCTEST, YARDSTICK), it is necessary to list terms used in project and give a detailed description to avoid confusion.

Here is the table  showing current terms in project.

If you feel any word is unclear , you can put it into this table, so we can review and discuss these terms constantly

Welcome recommendations and comments.

...

Recommend not using the word certification, nor cert, in our tools or documents.

(to use "compliance" instead of "certification"? MatthewLi)

...

Lets not use the term scenario.  Can we adopt "test suite" instead?

(agree, should think out name to replace this "scenario", since in OPNFV, "scenario" has special meaning MatthewLi)

...

how does this differ from "test suite", is this a "test area"?

(I'm not sure the initial idea of this name, but in current implementation, it means test case from other projects; for example, in dovetail.ipv6.tc001.yml , script test case is 'tempest_smoke_serial' which is smoke tier test case in functest )

...

"SUT_IP" may be a candidate

(agree SUT_IP, MatthewLi)

...