Wiki

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
==== Project Name: ====

  * Proposed name for the project: ''OPNFV Compliance Testing''
  * Proposed name for the repository: ''affirm''
  * Project Category: 
    * Integration & Testing

==== Project description: ====

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.

==== Scope: ====

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.

== Entry level OPNFV ==
 
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: 
  * Applications (VNF's) – the VNF can be deployed on an OPNFV/Pharos platform and reach an operational state
  * Hardware – The hardware is able to be configured to Pharos specs and supports the deployment of the platform 
  * Platform – the platform is able to be deployed on an OPNFV Pharos compliant hardware

== OPNFV Compliant ==

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:
  * Applications (VNF's) – the application can be deployed on any OPNFV/Pharos platform passing functional, security, portability & robustness requirements
  * Hardware – The hardware is able to be configured to Pharos specs and supports the deployment of any OPNFV platform passing functional, security & robustness certification
  * Platform – the platform is able to be deployed on any OPNFV compliant hardware passing rigorous functional, security & robustness tests

== OPNFV Ninja ==

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.  
  * Applications (VNF's) – the application can be deployed automatically on any OPNFV/Pharos platform passing functional, security, “performance”, robustness, portability, scalability & stability requirements
  * Hardware – The hardware is able to be configured to Pharos specs and supports the deployment of any OPNFV platform passing functional, security, performance & benchmarking certification
  * Platform – the platform is able to be automatically deployed on any OPNFV compliant hardware passing rigorous functional, security, performance, benchmarking, robustness & API certification

==== Testability: ''(optional, Project Categories: Integration & Testing)'' ====

  * The compliance testing will be executed by selecting relevant use cases and scenarios from other test and integration projects including but not limited to:
    * functest
    * qtip
    * Transformer* (if implemented)
    * Yardstick* (if implemented)

==== Documentation: ''(optional, Project Categories: Documention)'' ====

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:
  * Compliance process descriptions and parameters for each compliance level
  * Test specifications for each compliance level

==== Dependencies: ====

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.

==== Committers and Contributors: ====

Names and affiliations of the committers
  * Wenjing Chu (Wenjing_Chu@DELL.com)
  * Christopher Price (christopher.price@ericsson.com)
Names and affiliations of any other contributors
  * .

==== Planned deliverables ====

  * Described the project release package as OPNFV or open source upstream projects.
  * If project deliverables have multiple dependencies across other project categories, described linkage of the deliverables.

==== Proposed Release Schedule: ====

  * Entry Level OPNFV compliance testing is planned to be available for release 2 of the OPNFV platform
  * OPNFV compliance level testing is planned to be available for release 3 of the OPNFV project
  * OPNFV Ninja compliance level testing is planned to be available for release 4 of the OPNFV project
  * Each of these level will be maintained and further refined through future OPNFV releases
Wiki

User Tools

Site Tools

Page Tools
