The Linux Foundation Projects
Skip to main content

Join us at ONE Summit 2024 in San Jose and explore the latest in networking and edge innovation | REGISTER

By Amar Kapadia

(This post originally appeared on the Aarna Networks blog)

There was an LFN Developer Design Forum (DDF) and Plugfest held in Stockholm in early June. These is a semi-annual event. In the past, the ONAP project had conducted DDFs and OPNFV had conducted Plugfests. This event was the first for all LFN projects. Given the history though, bulk of the activity was around ONAP and OPNFV. Here are 5 key takeaways from the event:

 

  1. OVP: The community made great progress on the OPNFV Verification Program (OVP). Even though the name contains the word OPNFV, the program is broader than that. OVP started with an NFVI verification program and it now also includes VNF verification for ONAP.

  2. ONAP real-world experience: 8 end users (AT&T, Bell Canada, China Mobile, Orange, Swisscom, Telstra, Telecom Italia, and Vodafone) provided concrete feedback on ONAP requirements. In addition, there was discussion on use case blueprints for 5G, edge computing, residential connectivity (BBS), cloud native network functions, network-as-a-service (CCVPN), and more.

  3. ONAP planning: Various ONAP sub-projects and initiatives planned their activities for the next releases, El Alto and Frankfurt. El Alto is mostly expected to be a non-functional release focusing on S3P (scalability, security, stability, and performance) while Frankfurt will be a full blown release with functional and non-functional enhancements.

  4. ONAP 3rd party collaboration: The ONAP community discussed how to work more closely with 3rd party standards groups such as ETSI, TM Forum, 3GPP, MEF, Broadband Forum, and others. There were similar discussions on how to collaborate further with 3rd party open source projects such as CNCF.

  5. Other projects: OPNFV, OpenDaylight, and FD.io had discussions on their sub-project planning, upcoming releases, and non-functional enhancements such as scalability.

To learn more, read the full report.

Author