Page Comparison

-Policy-mariadb is no longer used by any project and can be removed

-Steps to remove unused repo

• Release notes: list repos removed with release
• LFIT: remove repo from jenkins jobs
• OOM: update integration & test scripts; remove disabled code
• Release mgr: update info.yaml to unmaintained; mark repo unmaintained

-RACI matrix: https://wiki.onap.org/display/DW/Project+State%3A+Unmaintained

Byung to re-gain access to O-RAN.

-Bob will socialize python & javascript POCs with PTLs

-Use language indicator on SonarCloud dashboard to determine programming language

• Example: https://sonarcloud.io/organizations/onap/projects?sort=-size&languages=jsp see Languages under filters
• Example: https://sonarcloud.io/project/issues?resolved=false&id=onap_clamp select Languages in second column

dcaegen2-collectors-ves SBOM successful

CPS SBOM failing because project not following ONAP versioning rules

Use cases to be added, limited resources to go with E2E solution integration.

Weekly meetings: https://wiki.lfnetworking.org/pages/viewpage.action?pageId=50528282

Architecture: https://wiki.lfnetworking.org/pages/viewpage.action?pageId=53609061

Roadmap: https://wiki.lfnetworking.org/display/LN/5G+Super+Blueprint+Roadmap

Requirements and Use case Advisory Group: https://wiki.lfnetworking.org/display/LN/Requirements+and+Use+Case+Advisory+Group

Use cases: https://wiki.lfnetworking.org/pages/viewpage.action?pageId=68792322

Use cases to be added, limited resources to go with E2E solution integration.

ØNext meeting later today, resource assignment needs to be done

Secure slicing needs to be better defined.

Major focus on setting up 5G with open source components.

Muddasar tasked with specifying detailed use case requirements for creating secure slices: least privilege

Eric Kline performing streaming analytics on data to use in closed loop slicing automation

Ericsson OOM team is focused on the ONAP security reference implementation.

Logging reference implementation is second priority work item for now.

Code link was shared with SECCOM before (nordix), but not yet contributed to ONAP

PTL meeting – August 15th

Meeting cancelled - bank holiday in part of Europe

TSC meeting – August 11th

-Confluence injection attack – plugin disabled

-DTF submissions, no deadline yet

Pawel and Amy submitted proposal: ONAP’s Recipe for Managing CVEs and Securing Open Source Software

Byung will present service descriptor and potentially new ONAP security architecture with service mesh.

Productization of Assured Opensource Software - Muddasar

SBOM implementation and challenges in ONAP - Muddasar

5G orchestration with ONAP, AI and ML. - Maggie

We start this topic.

The even-numbered versions of Node.js roll through “current” status, “Active LTS” status, and “Maintenance LTS” status. New releases come out every 6 months. So a current release becomes LTS 1 year later, then Maintenance LTS 1 year after that for an additional 1.5 years.

The current version is v18, the active LTS is v16, and maintenance LTS is v14. V14 is active through Apr 2023.

We should make sure that we are using Containers with Node.js v14, v16 or v20.

This MIGHT be automatic if we are using current node.js containers.

SECCOM MEETING CALL WILL BE HELD ON 23th 23rd OF August'22.