Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
We start our meetings by mentioning the project's Antitrust Policy, which you can find linked from the LF and project websites. The policy is important where multiple companies, including potential industry competitors, are participating in meetings. Please review and if you have any questions, please contact your company legal counsel. Members of the LF may contact Andrew Updegrove at the firm Gesmer Updegrove LLP, which provides legal counsel to the LF.
Agenda
START RECORDING
Duration
Agenda Item
Requested by
Notes / Links
Duration
Agenda Item
Requested by
Notes / Links
30 mins
Cross-project discussion
This meeting is reduced to 30 minutes
host: @Byung-Woo Jun
ONAP and LFN Collaboration
@Byung-Woo Jun
Discussions between Arpit Joshipura, Byung-Woo Jun, Jill Lovato, Louis Illuzzi and Sunny Cai:
Highlight the value proposition of ONAP, including overall statistics (e.g., contributors, LOC, etc.) over its lifetime.
ONAP TSC, ARCCOM, OOM, PTLs and SECCOM need to formalize processes for making semi-standalone projects (architecture, CI/CD, Project Release Cycle, Normalized APIs, Security, documentation)
Our proposals (Byung discussed them with Arpit, Ranny):
ONAP Organization Chart.
The ONAP function will have a more descriptive namespace / prefix for external clients.
For the time being, OOM provides a lot of useful services for the ONAP projects. Therefore, common services and OOM would be included by default.
However, telecom operators may choose alternative integration options. For example, if they prefer to use their own security, secure communications and CD (ArgoCD, Flux), those choices will not be precluded.
We plan to provide comprehensive documentation to support these options.
The current common helm chart repo needs to be separated per project.
The ONAP TSC, ARCCOM and SECCOM will oversee ONAP projects to ensure best practices, a uniform architecture, and strong security.
The ONAP Documentation team will continue to provide official ONAP documentation for now.
Currently, ONAP project functions are decoupled from security, secure communication and deployment, giving operators flexibilities.
ONAP projects will continue to be modularized, enabling sub-components to be selected at or after build time. This provides operators with greater integration flexibility based on their use cases.
ONAP projects should aim to minimize their dependencies to other projects.
Project with PTLs:
The projects are active, with new features continuously being added
The project PTLs control the project release cycles in an agile manner
Projects will have their own versions (e.g., Helm Chat versions, release versions) based on features and development cycles.
Documentation will be updated actively
Projects without PTLs:
These projects are not deprecated yet because other ONAP projects still use them.
There are no active feature enhancements, but software packages are updated to mitigate software vulnerabilities.
DT volunteers to handle software package upgrades for SDC, AAI, DCAE and MultiCloud, for the time being.
Once each project decouples its dependencies from projects without PTLs, those projects could become candidates for deprecation in the future.
Some Documentation will be managed by the ONAP TSC, ARCCOM and SECCOM as needed.
The concept of elevating ONAP modules to semi-standalone entities was presented to the board and got positive feedback. One request that did come up was to clarify the evolution of the integration tests that are currently part of the ONAP-wide release process (will they still exist in some form to ensure interoperability between the independent modules?). The next step would be executing the necessary changes in the ONAP CI/CD system. I see that @Byung-Woo Jun already has a sessions planned for the ONAP DTF Day (https://lf-onap.atlassian.net/wiki/x/mICKBg ) to discuss the next level of details. @LJ Illuzzi and I will of course support from the LF side.
Also, credits go to Ciaran Johnston and Christian Olrog
At the ONAP DTF days, I plan to present the ONAP TSC roadmap and Architecture evolution, covering this concept. Working with DT and other ONAP participating companies, I have outlined how ONAP will enable the individual build and deployment of ONAP components under the ONAP Streamlining evolution; i.e., ONAP already supports these capabilities.
The current OOM enhancements led by Andreas Geissler for ONAP CI/CD and ONAP architecture, leveraging Argo CD were tested during the Oslo release by DT and ARCCOM. Now, DT plans to contribute to ONAP CI/CD further by using both Argo CD and Flux during the Paris release. Additionally, China Telecom, China Mobile and DT have integrated several core ONAP components, referred to as Lightweight ONAP solutions, for their 5G and upcoming 6G.
Over the past couple of years, under the ONAP Streamlining evolution led by me (Byung), we have established a solid foundation, which has proven to be valuable.
Furthermore, ONAP TSC and ARCCOM have already discussed the possible integration solutions by leveraging individually built ONAP components. We are currently in the process of formalizing integration procedures and developing use cases for higher-level solutions. Additionally, I proposed the Runtime CI/CD for ONAP, and it will be part of my ONAP DTF Days presentations.
I fully agree with this direction, and we are proud of the foundational work achieved through this evolution. More to come… We have seen the future 😊
I plan to present the evolution to the ONAP DTF Days, and I look forward to collaborating with you all.
We need documentation for formalizing this new evolution. such as each each project documentation, API, security, release cycle, etc.
ONAP DTF Days 2025
@Byung-Woo Jun
Byung-Woo Jun, created a page for ONAP DTF DAYs 2025; we plan to collect ONAP DTF session topics here before presenting them to LFN, and schedule for the event.
Declarative and Intent-based component operations by the Repository-based Network Automation : see the ideas from ONAP Architecture Evolution - 2025.pdf
@Byung-Woo Jun , plans to finalize high-level session topics at the TSC this week (hopefully) to set a DTF day schedule.
Implementing it simply requires it to be added to gerrit-merge.yaml in your repository, so that it runs in GitHub when Gerrit changes are merged to the HEAD branch.
PTL input? Please feel free to share your suggestions!
Byung-Woo Jun presented the brainstorm at the TSC meeting this week.
Brainstorm:
Ensure ONAP core components are focused and operate independently, from build to runtime
DT finishes Argo-CD based component independent deployment: @Andreas Geißler
Argo-CD /Flux are a DT choice, but ONAP can allow other CDs,
DT plans to productize some of the selected ONAP core components early next year in their TNAP production environment
Declarative and Intent-based component operations by the Repository-based Network Automation : see the ideas from ONAP Architecture Evolution - 2025.pdf
Make ONAP core components more autonomous and ready for use by both ONAP, LF and other external users
During New Delhi and Oslo releases, CPS and Policy achieved the OpenSSF Gold Badging status. Kudos to the team!
Continue to promote/facilitate other ONAP core components for the Gold Badging status (e.g., UUI, SDNC, A&AI, Portal-NG)
@Dan Timoney , @Keguang He@Fiete Ostkamp : are you interested in this Gold Badging? aiming silver badge for AAI
Incorporate more GenAI capabilities and use cases to the ONAP components, and promote the adoption of open-source LLM models and frameworks aligned with LF AI & Data and GenAI Commons
Collaborate with LF AI & Data GenAI Commons and Nephio GenAI for 5G and 6G
Open-source based models and controls
AI-Based Control Loop: @Dong Wang
AI Model-As-A-Service : @Keguang He
ETSI ISG NFV compliance for AI?
Foster inter-community collaboration with other LF communities, such as O-RAN and Nephio
SDNC enhancements (which is used by O-RAN OAM as is): @Dan Timoney
Resource-based Orchestration Pattern (leveraging CD and Operator)
Energy saving / monitoring : @N.K. Shankaranarayanan
Ensure the security of ONAP components and operations : @SECCOM
The latest security mechanism for communications (service mesh enhancements leveraging Istio and coming Ambient Mesh)
Deprecate unused sub-components and mitigate security vulnerabilities
Define a secure LFN CI/CD pipeline by leveraging OpenSSF-associated reference tools : @SECCOM
PTLs, please update your project contents for Paris
ARCCOM Goals
@Byung-Woo Jun
Focus and Independence of Core Components: Ensuring that ONAP’s core components are both focused and capable of operating independently, from build to runtime.
Independent Deployment with Continuous Deployment Tools: Implementing ArgoCD- and Flux-based Continuous Deployment (CD) mechanisms to facilitate independent deployment of components.
Architecture Evolution: Developing a declarative and intent-based component operation strategy through the Repository-based Network Automation concept.
Autonomy and External Usability: Enhancing the autonomy of core components to make them more accessible and usable by both ONAP, Linux Foundation (LF), and other external users.
Security Enhancements: Implementing the latest security mechanisms for communications, including service mesh enhancements leveraging Istio and the upcoming Ambient Mesh.
Deprecation and Vulnerability Mitigation: Identifying and deprecating unused sub-components while mitigating security vulnerabilities.
Last TSC meeting we discussed on kafka issue and it was updated that still work is in progress. All updates are mentioned in the ticket. Thanks, it seems to be working now (edited) ; done
IT-27801; Kevin Sandi, please take a look at this; working on it. will merge this morning and will test it.;
Found licenses in the 'License not determined' license threat group ('Not Provided'); Paweł Pawlak, contact the code originator to add the license header; Byung-Woo Jun will check it with Murali.
Last TSC meeting we discussed on kafka issue and it was updated that still work is in progress. All updates are mentioned in the ticket. Thanks, it seems to be working now (edited) ; done
IT-27801; Kevin Sandi, please take a look at this; working on it. will merge this morning and will test it.;
Found licenses in the 'License not determined' license threat group ('Not Provided'); Paweł Pawlak, contact the code originator to add the license header; Byung-Woo Jun will check it with Murali.
Whats the survey about? LFN is partnering with Linux Foundation Research to explore trends and priorities in open source networking. We're looking for insights from industry professionals to get a better picture of open source use, opportunities, and challenges in the telecom industry.
Call to Action- LFN is looking for community members to help staff the booth, as well as project or collaborative demos that we can showcase in the booth.
Reach out to Jill Lovato if you want to volunteer at the LFN booth or have a project or
