Date
Attendees
LF Staff: Jim Baker
Committee Members: Trevor Lovett Kanagaraj Manickam Marc Price Olivier Smith Patric Lind Rabi Abdel Ranny Haiby Victor Morales Georg Kunz Bill Mulligan Frederick Kautz @Srinath Reddy Trevor Cooper Lincoln Lavoie
Proxies:
Guests:
Agenda & Minutes
Review Work Stream Status
- WS01: Governance/Structure/Mktg, Badging Process and Framework[Primary Owner: CVC] Rabi Abdel Lincoln Lavoie Heather Kirksey
- WS02: Definition Requirements Activities (CNTT/ONAP/SDOs) [Primary Owner: CNTT] Bill Mulligan Trevor Lovett Ryan Hallahan Olivier Smith Fernando Oliveira
- WS03: Lab and tooling [Primary Owner ONAP+OPNFV+CNCF] Frederick Kautz Kanagaraj Manickam Trevor Cooper Ryan Hallahan
- WS04: A. Cloud Platform Conformance - [Primary Owner ONAP+OPNFV+CNCF] Cedric Ollivier Taylor Carpenter
- WS05: B3. CNF Compliance - ONAP Kanagaraj Manickam Catherine Lefevre Amar Kapadia Seshu Kumar Mudiganti Ranny Haiby Srinivasa AddepalliFernando Oliveira Byung-Woo Jun
- WS06: B1/B2. CNF Compliance - Cloud Native & Functional [Primary Owner CNCF Taylor Carpenter ] Olivier Smith Trevor Lovett
- WS08: B4/C - Performance: Trevor Cooper
CN OVP Current State/Level Setting
Badging Hierarchy and Supporting Projects
For each category, a CNF may be badged for 1 or more Sub-Categories. To receive a badge, you must pass the tests for at least 1 category.
| Category | Sub-category | Requirement Source | Conformance Definition | Tests* |
|---|---|---|---|---|
| Cloud Platform | CNTT Compliance | CNTT RA-2 | CNTT RC-2 | OPNFV CNF Conformance? |
| Performance Benchmark | CNTT RA-2 | CNTT RC-2?? | OPNFV? | |
| CNF | Cloud Native | CNF Conformance/CNCF TUG | CNF Conformance | CNF Conformance |
| CNTT Compliance | CNTT RA-2 | CNTT RA-2 | OPNFV | |
| ONAP Compliance | ONAP VNF/CNF Requirements | ONAP VNF/CNF Test Cases | VNFSDK | |
| Performance | CNTT RA-2 | CNTT RC-2?? | OPNFV |
* NOTE: Individual tests may come from other projects, but the assumption is the projects will own overall execution of tests
CN OVP Responsibilities
- Platform and process for the submission, review, and approval of test results
- Publishing of the public badge
- Ensure requirements and tests are sufficiently progressed to provide value as a badge to both vendors and operators
- Cross-coordinate with communities to help with alignment and avoid conflicting requirements w/in the badge
Requirement/Conformance Project Responsibilities
- Define the enumerated, testable requirements required for compliance
- Document the tools and configuration thereof to verify compliance
Test Project Responsibilities
- Provide test implementations to verify at least mandatory, testable requirements (may not be 100% coverage at first)
- Provide test results in a format compatible with OVP to support the review and badge approval (NOTE: If not possible other conversion options can be pursued or considered)