• Discussions between Arpit Joshipura, Byung-Woo Jun, Jilll Lovato, Louis Llluzzi and Sunny Cai:
• Arpit's input:
  • Highlight the value proposition of ONAP, including overall statistics (e.g., contributors, LOC, etc.) over its lifetime.
  • Provide deployment examples with links to DT, CMCC, Ericsson, and others
  • Emphasize the product integration of ONAP
  • Use headlines like: "From Control loops and Intent-based to full AI Orchestration and Management."
  • Highlight security contributions, such as those provided during the OPS 5G project by US Government for Networking slicing
    • Byung-woo Jun plans to add details about ONAP's service mesh and Ingress architecture and implementation
  • Address past criticisms of ONAP being too large and complex by emphasizing recent efforts, such as "streamlining microservices and modules, archiving legacy software, etc."
    • Byung-Woo Jun explained the ONAP Streamlining Evolution initiative to address these concerns
  • This is one shot we get. Let's make it BIG!
• Byung-Woo Jun, together with ONAP TSC members, will collaborate with Jill, Louise, Sunny to create compelling marketing catch points. 
• Byung-Woo Jun, Jill Lovato, Louise Lluzzi and Sunny Cai (and along with others) plan to hold an initial call sometime next week to outline our plans. I plan to invite other TSC members as neededByung intends to engage with TSC members following the initial discussion.

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 +

Byung-Woo Jun plans to present the brainstorm at the TSC meeting this week.

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 
  • 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)
  • Resource-based Orchestration Pattern (leveraging CD and Operator)
  • Energy saving / monitoring 
• 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

PTLs

• For the Paris release features, we need to discuss the package updates; who is doing what?

• The next Paris release schedule is TSC approved on 05 Dec 2024 , Release Planning: Paris 

  • TSC approved the current Paris release schedule on December 5th

  • An ArgoCD deployment to provide an alternative the helm deployment

  • RAN Simulator enhancement
  • Policy-OPA-PDP
  • MAAS
  • SDC Ruby upgrade
  • Project package upgrade
  • SDNC/CCSDK - need to upgrade Java 21 and Maven ; PTL, SECCOM and ARCCOM will handle this

• Long Term Release Roadmap

• https://jira.linuxfoundation.org/plugins/servlet/desk/portal/2/IT-27520 - waiting for Murali - on hold
• Error in Creating Releng Go Jobs as per guide
• Kevin Sandi, is working on it and waiting for Murali's input
• What is the current status? almost done by Kevin Sandi. Deena, Murali and Kevin need to work together to finalize it.
• Requesting guidance on adding goLang based project to Nexus IQ - Project Services Support - Service Project
  (IT-27561) - In Progress, https://jira.linuxfoundation.org/plugins/servlet/desk/portal/2/IT-27561
• Kevin Sandi, New JJB template for Golang CLM scan is ready for review and approval => https://gerrit.linuxfoundation.org/infra/c/releng/global-jjb/+/73372 , once that change is approved and merged by LF we can proceed to upgrade the GlobalJJB version at ONAP and then merge following change https://gerrit.onap.org/r/c/ci-management/+/139794
• Ramesh Murugan Iyer, Policy team will check vulnerabilities on direct dependencies; may need to open a ticket for the product (Sonatype) company; Kevin Sandi, asked Murali to send the test results before raising tickets; CycloneDX-based SBOM; may need a conversion between CycloneDX and SPDX;
• So far, LFN supports SPDX only for their pipeline SBOM. SECCOM will discuss it further with the LF team. We need a conversion between CycloneDX and SPDX.

Byung-Woo Jun

• SECCOM will review the Java 21, Python, and Maven upgrades from the security perspective. 
• How to deal with vulnerabilities. e.g., SDC, UUI - Angular dependency issues. Also, MPM
• SECCOM plans to discuss these issues with PTLs at the next SECCOM meeting (next Tuesday)