Page Comparison

Fiete Ostkamp : Chef dependency in SDC related to Ruby conflict (2.0 is pretty old)  

Atlanta, Georgia from October 22-23

Schedule: https://email.linuxfoundation.org/e3t/Ctc/RI+113/cZw--04/VW20421KRWSMW25H9dF35S2gmVwDG2D5j9vZYN70SktR3qgyTW8wLKSR6lZ3msW6f-nGc8jMw2WW6PLn8F5XylNbW5kHdzx1pMHtfW2ldjmB6-R-7zVq9SV73CRtNtW3VN9Gq8wcwlWW4Fn7pT1PzCz_W32P4RN40kW2bW2VgnfM63lsqhN4RkJdDg7q38W4G_b2n1WP-XGW2F4z262Xn7F1W76GYT18zQGYZW8jj8h993XpPdW2kWrbS5PFXd9N86SL4hfqQG9N4hp9_Qz682JW1QPNg577TNNXW44YFbY2-2hwvW8BdZw75VVmXPN5ZdyPZ-8_nkW7ctCB37wg7yGW53chgq2lb9t6Vgg5sm37sNb8W4QdqX16qwWQCW7ld23P8qQgtVW3Yb-Bm1qr2p3N53g5VPf849qf1-JnKn04

Registration: 

https://email.linuxfoundation.org/e3t/Ctc/RI+113/cZw--04/VW20421KRWSMW25H9dF35S2gmVwDG2D5j9vZYN70Sktx3qgyTW7Y8-PT6lZ3lkW45CttV8xzKzMW8yq06x86dZvCW2ZY_J97ykfKdW4mlsVn7twbjNW3f0vrT2y-BcXV8dkBl29ZQptW4MmWwR7s8RPTW3PZgTh1J3J1wW7Sb0pj4gTvc2W7WTqDG7ppkY3W7PQzrt1ZcKzVW7-szSQ33Jfs5W8J_55Z6yGxVyW7ZzCXh7TV5C1W2W8cqn7fyyHbW2NDp1c4vw7xgW1syX951_FkwWW7c53XW8x_44KW4J1Fdx7KJyBvW7LkKhM98YtnJW5Zn8Gj3vvP0GW70JNRC2FsjkgW15lx-j3ksW5XW3TzmqM22JJtgW8WdlrM2VCmMgW3KxXtS5QgdXbf6T2YKH04

Support for Ramesh and Policy team to get gold badge.

List of people to be Policy page editors in the badging - done

Ticket opened by Tony: IT-26848 - Tony is checking on it, still has issues?

Issue still exists.

• On Amy's to do list: updating Java, Python, OS, database and utility versions (Amy) + creating Jira tickets for packages upgrades.

Mateusz Pilat from Tata presented changes in log format for its unification. Change Request will be prepared by Mateusz. Discussion will be followed at the OOM meeting on Wednesday.

RBAC changes could be provided: Improvement for NewDelhi Release

Root access for container need was explained.

• Maggie, Justin and Andrew Lamb's input: 
  • ONAP application services will run in a namespace whose privilege and security context are restricted via Pod Security Standards Restricted policy to meet the CIS 1.6 benchmark. No workloads in this namespace will ever be permitted to run with privileges or as root within the container.
  • ONAP logging services will run in a separate namespace which allows Pod Security Standards Privileged profiles. Any workload in this namespace will be permitted to run with privileges. To mitigate the risk of such a namespace, the Kubernetes Admission Controller, via Kyverno policies, will enforce strict admission requirements on workloads in this namespace.
  • To be deployed into the privileged namespace, workloads must be running a specific container image with restrictive container startup commands and arguments, as specified in Kyverno policies written by ONAP developers. This will ensure that only ONAP SECCOM approved workloads are ever permitted to run with privileges in this namespace.
• As a more general SECCOM note, Byung - I discovered in my research that the Kyverno admission validation hook can also (1) enforce minimum versions of container images (which I wish I would have known when trying to keep log4j off my clusters last year) and (2) prevent exec operations into running containers - this would be useful in preventing an insider from accessing the privileged workload once it has already been admitted to the privileged namespace. I did not include these because they seem to be larger design requirements for cluster administrators beyond just the management of ONAP. If you think it would be within ONAP's purview to enforce these mechanisms I'm happy to include them in the next PoC iteration. - Justin
• Hope in Oslo, we can discuss/explore this further.

Further update will be discussed during Oslo. Tata Communications still plans to do some improvement for Oslo, but no detailed plan yet.

LF IT migrating CI pipeline to GitHub actions - may take to the end of fall or later, once ONAP is completed for GitHub Actions , we will do security review. Last update from Matt is that LF IT is continuously shipping one project at a time. 

4/2: in progress

At the TSC Jess mentioned Q4'24? or rather beginning of 2025.

Need to write LF informative position white paper for AI/ML - team to write constituted. Meeting is planned with convenient time for all contributors. Goal is to produce it by DTF.

Structure bulleted paper available on Confluence - https://wiki.lfnetworking.org/pages/viewpage.action?pageId=120652848

China Mobile focus: generative AI. (New Delhi UUI)

China Telecom focus: intent transformation & LLM tuning parameters to create domain specific solutions. (New Delhi UUI)

Both projects are in progress.

Oslo lightweight model 

China Telecom and China Mobile presented at the last TSC their plans for AI/ML use cases with ONAP.

• China Mobile: "Intent Driven Orchestration for Autonomous Networks Leveraging GenAI, Nephio & ONAP" 
• China Telecom: "Exploration on Orchestration and Management of 6G mobile networks based on ONAP architecture"

By beginning of August both companies plan to present their plans for Oslo in this domain.

LFN AI-ML Use case formulation.pptx

Workload  identity and access management in progress. Internal discussions in E/// for next steps for user identity and access management.

• Workload Identity User Story, https://docs.google.com/document/d/1nkh7tTItwii1bY877PfzjFCBtmRos4IDh5EOJxWXRdg/edit#heading=h.srlm9p7wuua8
• Shiv plans to provide a better definition of "token".

Nephio R3, there is an action point, secret management, "sharing secrets across clusters as Skupper generates a secret in one cluster/namespace and that secret has to be shared with another cluster/namespace. To create the tunnel for communication. Now the question is how to share the secrets" It is a narrowed scope of sharing secretes between particular services, which is different from what Nephio SIG Security proposed.

Byung-Woo Jun , The Nephio SIG Security team (Shiv from Accuknox) plans to provide a demo of workload identity with SPIFFE this or next week. I will share the detail after their demo.

LF IT support is needed for SBOM SPDX format generation. Jess has experience with java based projects, and Nephio is Go based.

Byung-Woo Jun , Nephio O-RAN Workload Identity proposal by Nephio SIG Security will be presented to Nephio WG 2 ORAN on May 29th (postponed to June 5the), https://docs.google.com/presentation/d/1kofOHWswM2_OJPfefTcSzVvsBAg0QE3Z7GQITlaPO2w/edit#slide=id.p

Nephio Workload Identity execution plan:

• Start with PoC / demo to the relevant groups
• Requirements / user stories to SIG-1
• Detailed demo / run-through to SIG-Automation

Nephio update 2024-5-28:

• Signed image handling thru Nephio CI
• Nephio SGI security team is working on the above execution plan
• Nephio O-RAN workload identity proposal to Nephio WG 2 ORAN this week
• ORAN integration discussion (Q&A) further this week

Update xpected on 18th of June - Nephio signed image is a work in progress

Branch selected for Workload Identity - WIP.

• 2nd Demo for Workload Identity automation expected this week. 
• ORAN ZTA pdf: https://mediastorage.o-ran.org/white-papers/O-RAN.WG11.ZTA%20for%20Secure%20O-RAN%20White%20Paper-2024-05.pdf

Links shared by Muddasar:

https://datatracker.ietf.org/doc/bofreq-richer-wimse/

https://www.ietf.org/archive/id/draft-gilman-wimse-use-cases-00.html

Small demo presented with Vault used for secrets.

https://istio.io/latest/docs/ops/integrations/spire/

The second demo topic on July 23rd, 2024:

• Spire Server Agent created as part of the Nephio Install
• Node attestation for nodes in other clusters
• Node attestation for regional/edge clusters initiated by workload identity reconciler
• Library getting SVID, authenticating to vault, reading and writing to Vault
• Secrets CSI controller

Another demo on July 30th, 2024:

• SPIRE agent installed on all nodes via Damonset - how is registration of new nodes handled at scale?
• SA token is applied to SPIRE agent
• Spire-bundle is contained in a configmap for the spire agents to talk to the spire server
• How to prevent spoofing the SPIFFE ID/SVID? The current mitigation is JWT is 5 mins

Image Modified

Image Modified

New hydration concept = customization of CRD.

Byung-Woo Jun TATA Communications supports RBAC, observability, logging, backup, etc. by leveraging the ONAP currently security mechanism (Ingress, Service Mesh) for their own platform. It is possible they contribute the enhancements they made to the ONAP New Delhi release (TBD).

Share of code most probably in Oslo release. Andreas is working on enhancements for OOM Team.

Tata communication shared which components in Montreal use STDOUT or not, ONAP Logging alignment for Montreal release.xlsx

Postponed to Oslo.

Ambient mesh under consideration if stable and memory safe.

Trigger with ISTIO implementation to be detailed.

A plan for eBPF via Cilium, see Andreas' wiki page ONAP "Networking" Options (>=Kohn) For now, it is a consideration only.

DT on hold in general on hold with Ambient mode, for ONAP Andreas will continue.

Project Status in Oslo Release

TSC voted: TSC recommends all ONAP community members to add links with zoom meeting recording from Dashboard to ONAP Wiki's meeting summaries, so we could avoid an issue of high volume attachments with meeting recordings.

CNTI approved as  project. Paraglide might prepare presentation. - Next meeting on July 10th.

KPIs in project promotion and with health check discussion with every project. Chair and vice Chair election. Security seat and Superblueprint seat.

Proposal: use Tony's 5 year assessment as a baseline.

Planning meeting done last week.

WIP for Superblueprint.

New Use case under consideration (software packaging?)

Muddasar Ahmed to check for document availability on software quality goals.

Muddasar Ahmed to follow with Jill.

Muddasar Ahmed to follow with Jill.

Andreas was informed about lack of Jenkins jobs for Nexus-IQ scans. Fiete will work on this as project PTL.

Update from Fiete Ostkamp :

• maven based jobs use the lf-infra-sonatype-clm Jenkins builder that triggers the com.sonatype.clm:clm-maven-plugin
• for gradle there currently is no such builder available in global-jjb
• Sonatype officially does not provide an equivalent plugin, but there is the Sonatype Scan Gradle Plugin that could provide similar functionality

Jira opened by Fiete, ongoing support by LF-IT. Fiete is back from holidays.

Update from Fiete:

onap-portal-ng-preferences:

https://nexus-iq.wl.linuxfoundation.org/assets/index.html#/applicationReport/onap-portal-ng-preferences/b50d4e842a0847bc91437d354075e383/policy

onap-portal-ng-history:

https://nexus-iq.wl.linuxfoundation.org/assets/index.html#/applicationReport/onap-portal-ng-history/03f1fde4f7ea4f029031bbaf9689cfa8/policy

onap-portal-ng-bff:

https://nexus-iq.wl.linuxfoundation.org/assets/index.html#/applicationReport/onap-portal-ng-bff/4d9a28df94eb4bad85d858fe72321dac/policy

Sonarcloud scans for NG Portal available - waiting for a resolution for Nexus-IQ and NG Portal UI.