This is an old revision of the document!
OPNFV Compliance Testing
The OPNFV compliance testing project (affirm) intends to define and provide a set of OPNFV related validation criteria for levels of OPNFV compliance that will provide for the evaluation of the use of OPNFV trademarks.
The project will incrementally define qualifications for compliance that establish the foundations of how we are able to measure the ability to run the OPNFV platform, how the platform itself should behave, and how applications may be deployed on the platform.
The project intends to implement three levels of compliance that provide a measure of alignment with the OPNFV project for hardware, NFV platform, and NFV applications. This compliance activities are not intended to be exclusive in nature, but are intended to provide a measure for the community on the maturity and capability of the OPNFV project and related offerings.
The process of compliance testing must be able to be executed in an in-house compliance process by companies wishing to evaluate their products. This may follow a process similar to the global certification forum (GCF) self certification procedures.
The entry level for OPNFV compliance is intended to be a set of evaluations that should provide a set of non-exclusive test cases providing a method of identifying the adherence of NFV solutions to the OPNFV projects activities and goals. This can include compliance testing, by execution of a basic set of mandatory test cases, of:
The compliance level is intended to be more challenging to achieve, this should focus on a variety of test cases that demonstrate the expected behaviors and characteristics of an OPNFV based solution including such functest as robustness and security. This may be implemented as:
This level is intended to be a comprehensive evaluation of the NVF system under evaluation, this will include all functionality and integration level testing and introduce an expected benchmarking evaluation to form part of the qualification.
All procedures and methods will be clearly documented and be delivered as part of every release process. It is envisioned that each release will incur some deviation on the expected procedures and as such all documentation requires the same labeling process as other release artifacts. Expected documentation includes:
The affirm project intends to work with and leverage all other integration and verification projects to help define a common toolkit of compliance test cases and establish procedures for testing.
Names and affiliations of the committers
Names and affiliations of any other contributors