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
Last revision Both sides next revision
project_proposals:opnfv_compliance [2015/03/25 17:36]
Christopher Price
project_proposals:opnfv_compliance [2015/09/01 10:09]
Christopher Price
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 OPNFV 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 Compliance. ​==+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 affirm 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 Compliance. ======+  * 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 demonstrae the expected behaviours and characteristics of an OPNFV based solution 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 Compliance ​======+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.
  
-The proposed highest level of compliance achieved here.  We’re not only talking about passing tests we are talking about passing benchmarks etc… +==== Documentation:​ ''​(optionalProject Categories: Documention)''​ ====
-Application validation – the application can be deployed automatically on any OPNFV/​Pharos platform passing functionalsecurity, “performance”,​ robustness, portability,​ scalability & stability requirements +
-Hardware validation – 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 validation – the platform is able to be automatically deployed on any OPNFV compliant hardware passing rigorous functional, security, performance,​ benchmarking,​ robustness & API certification+
  
-  * Describe ​the problem being solved by project +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. 
-  * Specify any interface/​API specification proposed,  +Expected documentation includes
-  * Specify testing and integration+  * Qualification process descriptions ​and parameters for all evaluations and levels 
-  * Debugging ​and Tracing ​ +  * Test specifications ​for all evaluations ​and levels
-  * Unit/​Integration ​Test plans +
-  * Client tools developed ​for status shows etc.  +
-  * Identity a list of features ​and functionality will be developed. +
-  * Identify what is in or out of scope. So during the development phase, it helps reduce discussion. +
-  * Describe how the project is extensible in future+
  
-==== Testability''​(optional,​ Project Categories: Integration & Testing)'' ​====+==== Dependencies: ====
  
-  * Specify testing ​and integration ​like interoperability,​ scalability,​ high availablity +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: 
-  * What QA and test resources ​will be available?+    * functest 
 +    * qtip 
 +    * Yardstick
  
-==== Documentation:​ ''​(optionalProject Categories: Documention)''​ ====+The dovetail project additionally intends to work with other related industry forums to best ensure the applicability and acceptance of the processesincluding but not limited to the ETSI NFV ISG TST working group.
  
-  * API Docs +==== Committers and Contributors:​ ====
-  * Functional block description+
  
-==== Dependencies:​ ====+Project Leader 
 +  * Christopher Price (christopher.price@ericsson.com)
  
-  * Identify similar projects is underway or being proposed in OPNFV or upstream project +Names and affiliations of the committers 
-  * Identify any open source upstream projects and release timeline.  +  * Christopher Price (christopher.price@ericsson.com) 
-  * Identify any specific development be staged with respect to the upstream project and releases+  * Wenjing Chu (Wenjing_Chu@DELL.com) 
-  * Are there any external fora or standard development organization dependenciesIf possible, list and informative and normative reference specifications. +  * Hongbo Tian (hongbo.tianhongbo@huawei.com)
-  * If project is an integration and test, identify hardware dependency.+
  
-==== Committers ​and Contributors:​ ==== +Names and affiliations of any other contributors 
- +  * Ashlee Young, Huawei (ashlee@onosfw.com) 
-  * Names and affiliations of the committers +  * Ana Cunha (ana.cunha@ericsson.com) 
-  * Names and affiliations of any other contributors+  * 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: ====
  
-  * When is the first release ​planned? +  * The dovetail project intends to participate in the Brahmaputra ​release ​providing a foundation for C&C qualification and plugfests 
-  * Will this align with the current ​release ​cadence +  * Further development and refinement will occur iteratively ​with each OPNFV release
- +
- +
-Use the above information to create a key project facts section on your project page +
-===== Key Project Facts ===== +
- +
-** Project Name: ** Project Name (repo name) \\ +
-** Repo name: ** \\ +
-** Project Category: ** \\ +
-** Lifecycle State: ** \\ +
-** Primary Contact: ** \\ +
-** Project Lead: ** \\ +
-** Jira Project Name: ** Same as Project name \\ +
-** Jira Project Prefix: ** [10 Characters max [A-Z] ] \\ +
-** mailing list tag ** [Should match Jira Project Prefix] \\ +
-** Committers: ** \\ +
-foo@bar.com \\ +
-baz@qux.com \\ +
-** Link to TSC approval: Example http://​meetbot.opnfv.org/​meetings/​opnfv-meeting/​2015/​opnfv-meeting.2015-03-03-15.01.html ** \\  +
-** Link to approval of additional submitters: ** Example http://​meetbot.opnfv.org/​meetings/​opnfv-meeting/​2015/​opnfv-meeting.2015-03-03-15.01.html \\ +
- +
- +
- +
- +
- +
- +
- +
- +
- +
-My top of mind thinking goes something like this:+
  
-This may be difficult to envision. 
-But I see the need to define and develop each level as we go improving each but maintaining a set of target capabilities to be evaluated (which may evolve over time). 
  
project_proposals/opnfv_compliance.txt · Last modified: 2015/09/01 10:10 by Christopher Price