...
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.
- 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.
- 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
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.
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):
...
Encourage OPNFV integration projects and the upstream projects to integrate and test data path features/acceleration in OPNFV to enhance networking stack for all of the LFN community.
Encourage benchmarking of performances of various networking solutions for OPNFV use cases, e.g. Clover is trying to use tools like vsPerf and others like jMeter to conduct explainable benchmarking.
3) Micro-services support
...
7) Cross project collaborations
- Eat your own dog food. Encourage OPNFV projects consider containerizing their artifacts, supporting testing containerized solutions, adopting CI/CD, and service mesh.
- ONAP also aims to move to cloud native. We need to position OPNFV in helping ONAP achieve their goals without unnecessary replication.
- Auto project is working on running ONAP on OPNFV VIM. It will be beneficial to run ONAP as a cloud native application on OPNFV's cloud native infrastructure.
- FD.IO has goals in high performance data path for cloud native VNFs. We should investigate best way to integrate that as one of the acceleration methods.
- Akraino, a new LF project, is starting to work on edge software stack to support use cases in enterprise, IoT and operators that will have similar needs.
- The CD (continuous deployment) initiative is applicable for all projects within LFN, and related to upstream (CNCF, Openstack), and compliments to the XCI initiative, Lab-as-a-service/Pharos etc.
- Cloud native is a general theme that we should push together in LFN.
Recommendation #7:
Encourage OPNFV projects consider containerizing their artifacts, supporting testing containerized solutions, adopting CI/CD, and service mesh.
OPNFV should take a lead to drive a LFN cloud native initiative.
...
- Container4nfv (formerly OpenRetriever): Container4NFV
- Focused Focuses on containers, kubernetes
- Clover: https://wiki.opnfv.org/display/CLOV
- Focused Focuses on micro-services management, service mesh, CI/CD, sample VNF micro-services
- XCI: http://docs.opnfv.org/en/latest/infrastructure/xci.html
- Focused Focuses on cross-project CI
- Auto: ONAP-Automated OPNFV (Auto)
- Focused Focuses on ONAP on top of OPNFV's NFVI
- Edge cloud: Edge cloud
- Focuses on carrier scale edge cloud.
- FDS(FD.IO): https://wiki.opnfv.org/display/fds
- Several fronts in networking data path
- Installer projects that produce Kubernets scenarios: Apex, Compass, Joid
- Test projects/ Tesing Working Group - how to reuse test tools for cloud native
- Infra Working Group: How to allocate/use infra to support long running micro-services
- Doc: in OPNFV and cross LFN projects
...
Raw discussions during zoom meetings are captured in this etherpad: https://etherpad.opnfv.org/p/cnwg
new "OPNFV Cloud Native Working Group"