You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

Welcome the development space for the OVP 2.0 efforts.  This work was kicked off on November 5, 2019, minutes here: https://etherpad.opnfv.org/p/OVPp2_Kickoff

The purpose of this page is to develop the Mission, Scope, Objectives, and Roadmap for the program, ideally in that order and addressing the points raised during the kickoff meeting.

Mission

To promote the development of the next generation of OVP badges for infrastructure and cloud native network function, focused on supporting the telecom's adoption and deployment of cloud native technologies, including both container technologies and best practices.  The OVP badges must provide value to both operators and commercial vendors, where commercial vendors may be providing infrastructure platforms or cloud native network functions.

Scope

OPV program development specifically for cloud native technologies, both infrastructure and cloud native network functions.  Cloud native technologies should meet the following requirements to differentiate the OVP 2.0 program(s) from the existing programs.

  • CNCF TUG
    • Reqs, Guidelines, White Papers, etc.
  •  CNTT
    • Reference Model and Cloud Native based Reference Architectures.
  • Others (from other relative projects such as ONAP, etc)

The scope includes:

  • E2E Framework (Tooling, process, tests) to verify and certify cloud native infrastructure.
    • Requirement to come from CNTT, CNCF TUG, and regulatory - 3GPP.
  • E2E Framework (Tooling, process, tests) to verify and certify cloud native network functions.
    • Requirement to come from CNTT, CNCF TUG, and regulatory - 3GPP.
  • Gaps analysis.
    • Identify where gaps are and propose solutions.

Objectives

  • Drive simplification of cloud native network function adoption by standardising on certification and verification activities.
  • Offload internal verification of cloud native technologies (Infrastructure and cloud native network functions) and reduce cost of internal verifications.
  • Align with CNTT artefacts and empower it by providing E2E Framework for Certification and Verification of Cloud native technologies.
  • Laverage available upstream projects and align with industry Initiatives.

Plan

  • CNCF TUG meeting CNTT next week.
  • Jim to schedule time after the meeting to think about next step after the discussion has been taken place.

Roadmap


  • No labels