User Tools

Site Tools


project_proposals:opnfv_compliance

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
project_proposals:opnfv_compliance [2015/03/25 18:45]
Christopher Price
project_proposals:opnfv_compliance [2015/09/01 10:10]
Christopher Price [Scope:]
Line 1: Line 1:
 ==== Project Name: ==== ==== Project Name: ====
  
-  * Proposed name for the project: ''​OPNFV Compliance Testing''​ +  * Proposed name for the project: ''​dovetail''​ 
-  * Proposed name for the repository: ''​affirm''​+  * Proposed name for the repository: ''​dovetail''​
   * Project Category: ​   * Project Category: ​
     * Integration & Testing     * Integration & Testing
Line 8: Line 8:
 ==== Project description:​ ==== ==== 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 OPNFV testing project (dovetail) intends to define and provide a set of OPNFV related validation criteria that will provide ​input for the evaluation of the use of OPNFV trademarks.  The dovetail 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 ​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 incrementally define ​qualification criteria ​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: ==== ==== 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.+The project intends to define and implement ​as necessary qualifications ​that provide a measure of alignment with the overall ​OPNFV project for hardware, NFV platform, and NFV applications.  ​The qualifications ​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 established processes and tools should be derived from available open source components and test cases. ​ Testing should be able to be executed in an automated on-premise 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 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 inital scope of the dovetail project ​for OPNFV 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 should ​include ​qualification ​by execution of a basic set of mandatory test cases focused on proving
-  * 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 ==+  * Lab ready trademark qualification test suites 
 +  * OPNFV feature and interface level testing  ​
  
-The compliance level is intended to be more challenging to achieve, this should focus on 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: +Additionally the project will define ​set of pre-requisites,​ an execution process and reporting guidelines for running the associated ​test cases.
-  * 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 == +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.
- +
-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)''​ ==== ==== Documentation:​ ''​(optional,​ Project Categories: Documention)''​ ====
Line 49: Line 33:
 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. 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: Expected documentation includes:
-  * Compliance ​process descriptions and parameters for each compliance level +  * Qualification ​process descriptions and parameters for all evaluations and levels 
-  * Test specifications for each compliance level+  * Test specifications for all evaluations and levels
  
 ==== Dependencies:​ ==== ==== 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.+The dovetail ​project intends to work with and leverage other integration and verification projects to help define a common toolkit of test cases and establish procedures for testing.  The tests will be derived from relevant use cases in other test and integration projects including but not limited to: 
 +    * functest 
 +    * qtip 
 +    * Yardstick 
 + 
 +The dovetail 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:​ ==== ==== Committers and Contributors:​ ====
 +
 +Project Leader
 +  * Christopher Price (christopher.price@ericsson.com)
  
 Names and affiliations of the committers Names and affiliations of the committers
-  * Wenjing Chu (Wenjing_Chu@DELL.com) 
   * Christopher Price (christopher.price@ericsson.com)   * 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 Names and affiliations of any other contributors
-  * .+  * Ashlee Young, Huawei (ashlee@onosfw.com) 
 +  * Ana Cunha (ana.cunha@ericsson.com) 
 +  * Marko A. Kuisma (marko.a.kuisma@nokia.com) 
 +  * Mika Rautakumpu (mika.rautakumpu@nokia.com)
  
 ==== Planned deliverables ==== ==== Planned deliverables ====
  
-  * Described the project release package as OPNFV or open source upstream ​projects. +  * A well defined process for OPNFV qualification and validation testing. 
-  * If project deliverables have multiple dependencies across other project categories, described linkage of the deliverables.+  * 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: ==== ==== Proposed Release Schedule: ====
  
-  * Entry Level OPNFV compliance testing is planned ​to be available for release 2 of the OPNFV platform +  * The dovetail project intends ​to participate in the Brahmaputra ​release ​providing a foundation ​for C&C qualification and plugfests 
-  * OPNFV compliance level testing is planned to be available for release ​3 of the OPNFV project +  * Further development and refinement ​will occur iteratively with each OPNFV release
-  * 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 ​+
  
  
project_proposals/opnfv_compliance.txt · Last modified: 2015/09/01 10:10 by Christopher Price