All members are encouraged to contribute directly into this working draft. See also the OVP 2.0 Technical Ideas page
| Table of Contents | ||
|---|---|---|
|
...
- Open NFVI project (OPNFV)
- Open Networking Automation Project (ONAP)
- Compliance and Verification Committee (CVC)
Common NFVI Telco Taskforce (CNTT)
Cloud Native Computing Foundation (CNCF)
- Telecom User Group (TUG)
- CNF Conformance
5G Cloud Native Network Demo (Brandon Wick)
...
- A. Cloud Platform Conformance
- A1. Performance/Non-functional (security/resource utilization/etc):
- A2. Functional:
- A3. Cloud Native:Functional (i.e. CNTT RA-2 Compliance)
- B. CNF On-boardingConformance
- B1. CNF Compliance: Packaging: (Helm v3.0, TOSCA, HEATCloud Native (i.e. CNF Conformance)
- B2. CNF LCM: CNF Metadata for on-boarding and LCM
- C1. Performance:
- C2. Functional:
- C3. Cloud Native: . Functional (i.e. CNTT RA-2 Compatibility)
- B3. ONAP
- B4. Performance
- C. Cloud Platform Benchmarking
MVP proposal
Not every thing can be tackled in the MVP, here are two elements that can be tackled for MVP.
- A1: Cloud Platform Conformance (may be partial)
- B1 & B2: CNF Compliance
What needs to happen/Decided on:
- Decide on Tooling:
- Cloud installation tools into a given lab.
- Basic Testing Tools.
- what open source project is responsible of this.
- Decide on Lab:
- Community development resource access
- Platform details - specific HW details, login info,etc.
- what open source project is responsible of this.
- Decide on Badging Process:
- Test results review process
- Portal and badging process
- Decide on OpenSource Testing Projects
- What project will deliver what test category (A, B, and C)
- A: ?
- B: ?
- C: ?
- What project will deliver what test category (A, B, and C)
MVP proposal
Not every thing can be tackled in the MVP, here are two elements that can be tackled for MVP.
- C3: CNF Cloud Native Conformance (Per CNCF CNF Conformance Characteristics):
...
(Should note that these are currently not characteristics that will be sufficient and/or accurate for Telecom use. As an example, in 5G the CHF (Charging Function) will be required to provide stateful transaction processing for services that are monetized on a metered basis – e.g. charging per minute for a live video chat session to a healthcare professional. It is unclear if these types of distinctions will be specified as work coming from CNTT.).
- B1: CNF Compliance.
Workstreams Proposal (see OVP 2.0 Workstreams)
- 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 F. Kautz IV Kanag Trevor Cooper Ryan Hallahan
- WS04: A. Category Testing (not essential for MVP) Cloud Platform Conformance [Primary Owner XX] Taylor Carpenter (cloud native)
- WS05: B. Category Testing [Primary Owner ONAP] Kanag Ryan Hallahan Trevor Lovett WS06: C. Category Testing B3. CNF Compliance - ONAP Kanag cl664y@att.com 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
WS07: ONAP POC and existing development work [Primary Owner ONAP ]cl664y@att.com Amar Kapadia Seshu Kumar Mudiganti Ranny Haiby Srinivasa AddepalliFernando Oliveira Byung-Woo Jun Merged with WS05- WS08: B4/C - Performance: Trevor Cooper
MVP Roadmap - NEEDS COMMUNITY REVIEW/UPDATE
...