Versions Compared

Key

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

...

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.

...

...