Passcode: 209247
We will 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.
| Attended | Proxy (w/ @name) | Holiday | Did Not Attend |
|---|
...
| Agenda Items | Presented By | Presos/Notes/Links/ |
|---|
Strategy (45 minutes) | ONAP takeaways |
| We are encouraging ONAP consumers to share with us their feedback, so we could prioritize our activities and make ONAP better suited their needs and requirements. |
|---|
LFN Cross-Organization UpdatesMAC, SPC, TAC, EUAG, LFN Board |
| |
TCC / ONAP Liaison Updates |
|
|
Task Force Updates |
|
|
TSC Strategy | Byung-Woo Jun TSC | From the Paris release, TSC needs to discuss ONAP focus areas and strategies / roadmaps - TSC members to add thoughts
Let's discuss more this year for Paris + Brainstorm: - Ensure ONAP core components are focused and operate independently, from build to runtime
- DT finishs Argo-CD based component independent deployment
- Argo-CD is a DT choice, but ONAP can allow other CDs, e.g., Flux (need contributors)
- 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 - Ideas (November 2023)
- 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)
- 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
- AI Model-As-A-Service
- 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)
- Resource-based Orchestration Pattern (leveraging CD and Operator)
- Ensure the security of ONAP components and operations
- 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
|
Operations (40 minutes)
| TSC Activities and Deadlines | LJ Illuzzi | |
|---|
PTL Updates | Dan Timoney Andreas Geißler Kevin Sandi Byung-Woo Jun | |
Oslo Release Status | Byung-Woo Jun LJ Illuzzi | |
Paris Release Status | Byung-Woo Jun | |
GoLang Job issues | murali parthasarathy k Kevin Sandi | |
RelEng/Infrastructure | Kevin Sandi Tony Hansen | - Any other pending issues
08:58:30 [ERROR] PublisherTest.publishEvent_shouldSuccessfullyPublishSingleMessage:81 expectation "expectNext(MessageRouterPublishResponse{successful=true, failed=false, items=List({"message":"message1"})})" failed (expected value: MessageRouterPublishResponse{successful=true, failed=false, items=List({"message":"message1"})}; actual value: MessageRouterPublishResponse{failReason=Topic topic not present in metadata after 60000 ms., successful=false, failed=true, items=List()})
|
Subcommittee UpdatesArch, Lab, Modeling, Seccom, Requirements | | |
SECCOM | Paweł Pawlak | |
Events & Meetings (5 minutes) | Upcoming Events & Housekeeping | LJ Illuzzi | |
...
