project_proposals:opnfv_compliance
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
project_proposals:opnfv_compliance [2015/08/17 12:43] Christopher Price |
project_proposals:opnfv_compliance [2015/09/01 10:10] (current) 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 testing project (affirm) 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 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 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 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. | 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. | ||
| Line 20: | Line 20: | ||
| == Initial (Brahmaputra) goals == | == Initial (Brahmaputra) goals == | ||
| - | 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: | + | 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: |
| * Lab ready trademark qualification test suites | * Lab ready trademark qualification test suites | ||
| Line 38: | Line 38: | ||
| ==== Dependencies: ==== | ==== Dependencies: ==== | ||
| - | The affirm 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: | + | 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 | * functest | ||
| * qtip | * qtip | ||
| * Yardstick | * 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. | + | 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: ==== | ||
| Line 58: | Line 58: | ||
| * Ashlee Young, Huawei (ashlee@onosfw.com) | * Ashlee Young, Huawei (ashlee@onosfw.com) | ||
| * Ana Cunha (ana.cunha@ericsson.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 ==== | ||
| Line 68: | Line 69: | ||
| ==== Proposed Release Schedule: ==== | ==== Proposed Release Schedule: ==== | ||
| - | * The affirm project intends to participate in the Brahmaputra release providing a foundation for C&C qualification | + | * The dovetail project intends to participate in the Brahmaputra release providing a foundation for C&C qualification and plugfests |
| * Further development and refinement will occur iteratively with each OPNFV release | * Further development and refinement will occur iteratively with each OPNFV release | ||
project_proposals/opnfv_compliance.1439815383.txt.gz · Last modified: 2015/08/17 12:43 by Christopher Price
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: Creative Commons Attribution 4.0 International License
