Cloud Native Working Group Proposal: (July 30, 2018)
The Task Force proposes that we establish a working group to help drive these recommendations to project deliverables and have them implemented.
1) TG's scope
- 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
- Establish a cloud native CD toolchain and process
- 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
- 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, ‘middle-box’ data path, edge support, etc.
Produce user oriented and developer oriented training material
Creation of a WG with the defined scope and proposed work items
Current task force members to kick start the WG
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):
...