Versions Compared

Old Version 22

changes.mady.by.user Former user

Saved on

compared with

New Version Current

changes.mady.by.user Frank Brockners

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

OPNFV Cloud Native Working Group Proposal

  • Scope of the new "OPNFV Cloud Native Working Group"
    • Serve as a forum to coordinate among all projects working on cloud native initiatives and drive for common goals and strategies

    • Serve as a common bridge with CNCF, ONAP/LFN, edge and other relevant communities. Represent OPNFV to work with these communities as a liaison and/or on joint initiatives.

    • Provide periodic updates to TSC

  • Work items and objectives of the new "OPNFV Cloud Native Working Group"
    • Initial work item / starting point:
      • Create a "world map of cloud native in OPNFV" (short presentation) - document cloud-native related OPNFV projects and efforts, their current status as well as plans.
        Outline how these projects fit into the larger cloud-native ecosystem / articulate relationships to other projects (e.g. CNCF) / identify opportunities for future work. 
    • Establish a cloud native CD toolchain and process
    • Drive commonalities among OPNFV k8s scenarios. Produce common Kubernetes scenarios (e.g. two) with long-live community environment
    • Work with projects (initially select a few) to help them
      • produce cloud native artifacts
      • adopt cloud native tools and practices
      • adapt/expand to support cloud native environments
    • Ensure new projects include cloud native where appropriate
    • Establish robust connection and engagement with upstream CNCF, ONAP/LFN, edge and other communities
    • Support multi-clouds based on k8s: e.g. ONAP, edge, public clouds

    • Drive longer term efforts: e.g. common API, service mesh, ‘middle-box’ data path, acceleration, edge support, etc.

    • Produce user oriented and developer oriented training material

We propose to identify some low hanging fruits for initial goals, and at the same time start to formulate and drive some of the longer term objectives.
Meeting time can be shared among the main projects involved to reduce overlap and may choose two alternating time zones to accommodate more participants. May look into existing WGs (Infra, Testing WG) for more best practices.
3) Ask from TSC

  • Creation of a WG with the defined scope and proposed work items

  • Current task force members to kick start the WG, WG is open to everyone interested in participating.

PS: Recommendation summary deck previously presented to TSC: Cloud native WG recommendations.pdf
==============================

Objectives:

OPNFV started the open source NFV journey largely based on a VM approach, specifically Openstack. This approach means more than just VM as basis of virtual compute unit, but also the implies a "virtual appliance" model. This model influences the overall architecture, software and service design philosophy in many aspects beyond the choice of hypervisors. Supporting cloud native for NFV, therefore, means supporting ALL of the following three aspects (as defined by CNCF and others):

...

Raw discussions during zoom meetings are captured in this etherpad: https://etherpad.opnfv.org/p/cnwg


new "OPNFV Cloud Native Working Group"