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 affirm project will be executed with the guidance and oversight of the Compliance and Certification committee and work to secure the goals of the C&C committee for each release.

The project intends to incrementally define qualifications for compliance that establish the foundations of how we are able to measure the ability to utilize the OPNFV platform, how the platform itself should behave, and how applications may be deployed on the platform.

==== Scope: ====

The project intends to define and implement as necessary compliance qualifications that provide a measure of alignment with the overall OPNFV project for hardware, NFV platform, and NFV applications.  The 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 established processes and tools should be derived from available open source components and test cases.  Testing should be able to be executed in an on-premise compliance process by entities wishing to evaluate their products or services.  This may follow a process similar to the global certification forum (GCF) self certification procedures.

== Initial (Brahmaputra) goals ==
 
The inital scope of the affirm project 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 focused on proving: 

  * Lab ready trademark qualification test suites
  * OPNFV feature and interface level testing  

Additionally the project will define a set of pre-requisites, an execution process and reporting guidelines for running the associated test cases.

Qualification for the use of the OPNFV trademark is not intended to be governed by the successful execution of the test cases at this time and will remain at the discretion of the Compliance and Certification committee.

==== 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 other integration and verification projects to help define a common toolkit of compliance test cases and establish procedures for testing.  The compliance tests will be derived from relevant use cases in other test and integration projects including but not limited to:
    * functest
    * qtip
    * Yardstick

The affirm project additionally intends to work with other related industry forums to best ensure the applicability and acceptance of the processes, including but not limited to the ETSI NFV ISG TST working group.

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

Project Leader
  * Christopher Price (christopher.price@ericsson.com)

Names and affiliations of the committers
  * Christopher Price (christopher.price@ericsson.com)
  * Wenjing Chu (Wenjing_Chu@DELL.com)
  * Hongbo Tian (hongbo.tianhongbo@huawei.com)

Names and affiliations of any other contributors
  * Ashlee Young, Huawei (ashlee@onosfw.com)
==== Planned deliverables ====

  * A well defined process for OPNFV compliance testing.
  * Necessary test cases to be implemented in relevant OPNFV test projects.
  * A well define test specification and tool-chain to be used for compliance testing deriving from existing OPNFV test suites.

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

  * The affirm project intends to participate in the Brahmaputra release providing a foundation for C&C qualification
  * Further development and refinement will occur iteratively with each OPNFV release
Wiki

User Tools

Site Tools

Page Tools
