2025-03-18 Meeting notes - Joint OAM / NONRTRIC / SIM Community meeting

No meeting. Only a few attendees - so just an informal chat for a few minutes. 

Note: Meeting has now moved to our new "Summer" time: 15:00 UTC. Please check the calendar:

• https://lists.onap.org/g/onap-meetings/calendar

• https://lists.o-ran-sc.org/g/main/calendar

Time & Location:

Anti-Trust Notice

• Antitrust Policy Notice

• Antitrust Policy

Date

Mar 18, 2025

Attendees

• @Alex Stancu

• @Martin Skorupski

• @John Keeney (Ericsson EST)

• @fransiscus bimo

• ... others. Please add yourself

• May not have captured a full correct attendee list for this meeting  ... please add/remove yourself

See also / co-located (ONAP/O-RAN-SC/SMO - Meeting)

• Co-located with ONAP 2025-03-18 Meeting notes (ONAP/O-RAN-SC/SMO - Meeting) (Cancelled) 

Contents

Recording

Notes:

Housekeeping:

• Next Meetings:

  • Somehow meetings were cancelled in calendars. @John Keeney (Ericsson EST) will re-add

  • Daylight Savings Time kicks in in US this week.

    • From THIS week - Move to 15:00 UTC

      • One Hour earlier for some people in Europe for the next 3 weeks - until DST time change happens in Europe & other places

      • One Hour earlier for all attendee from some countries that do not use Daylight Savings Time - In particular time is better for Asian participants. 

• Calendar: 

  • https://lists.o-ran-sc.org/g/main/calendar

  • https://lists.onap.org/g/onap-meetings/calendar

    • Issue with Calendars this week! - Will fix.

    • Will update invites according to Daylight Savings Time changeover. See above. 

• OSC SMO project calls now move to its own time slot - alternate Thursdays

  • See OSC RSAC Calendar: https://lf-o-ran-sc.atlassian.net/wiki/display/RSAC/calendars

  • See also OSC Meetings calendar: https://lists.o-ran-sc.org/g/main/calendar

  • (Note this meeting to open to anyone, including non-ORAN members)

  • We will maintain this slot for ONAP Alignment, and try flag issues/question to/from SMO meetings.

  • See OSC SMO Project meeting notes

• See also OSC AIML Project meeting notes

OSC Project roundup:

News from OSC TOC & OSFG & RSAC calls last week

• TOC:

  • https://lf-o-ran-sc.atlassian.net/wiki/display/TOC/#ORANSCTechnicalOversightCommittee(TOC)

  • Last week's TOC (Thursday):

    • Trying to find a good candidate for OSFG community meeting

    • OAI Summer workshop

    • CVEs process: see Common Vulnerabilities and Exposures (CVE) 

  • This week's TOC (Thursday):

    • Workshop in coming months?

• OSFG: (@Martin Skorupski)

  • No meeting this week

  • No update or significant progress this week

• RSAC (@Martin Skorupski )

  • Minutes: RSAC Meeting notes

  • Moving slots for the RSAC meetings occuring during night Europe-time. Suggestion to move to early Europe time - still possible for Asian attendees (late), but no possible for most US. 

  • No nomination yet for 2nd RSAC CoChair (with @Martin Skorupski) now that @Rittwik Jana is stepping down 

NONRTRIC (@John Keeney (Ericsson EST))

• Small Update this week: See previous weeks:

  • Wrapping up loose ends for last release. - documentation, testing, deployments etc.

    • Ref Release K

  • Scope for L Release still being considered. Likely reduced from previous releases.

  • End-to-end demo & issues: @Martin Skorupski @Alex Stancu @Sridhar Rao

    • @Alex Stancu created a couple of Jira tickets

      • https://lf-o-ran-sc.atlassian.net/browse/NONRTRIC-1048

      • https://lf-o-ran-sc.atlassian.net/browse/NONRTRIC-1047

      • https://lf-o-ran-sc.atlassian.net/browse/INT-161

      • Related to https://gerrit.o-ran-sc.org/r/c/nonrtric/plt/ranpm/+/13974 from @Sridhar Rao ?

      • Don't think a new repo is needed. Will try incorporate changes into existing functionality.

      • Since datafilecollector can run multiple instances, should be okay to have multiple formats for different instance. Controlled by a config option?

    • @Alex Stancu & @Sridhar Rao still comparing notes, and @Aravindhan Ayyanathan & @John Keeney (Ericsson EST) examining Sridhar's PR (above) to try merge it into NONRTRIC RANPM.

    • Email from @Sridhar Rao about issue startingRANPM docker-setup  charts due to a version problem with OPA.

      • Leads to topic creation failure due to un-authorized.

      • @John Keeney (Ericsson EST) will investigate further & create a ticket if needed.

      • @Sridhar Rao suggests pinning OPA version to  0.70.0-envoy-12 

• @Aravindhan Ayyanathan working on integrating @Sridhar Rao & @Alex Stancu PM file & ves collector format.

  • Will work on this for this release - Making good progress - Done!

• Working on Integrated charts for SMO install

  • Making good progress on this - and would like to be able to release charts.

  • ... Its very difficult to run demos otherwise - need to build a new environment every time!

  • See also starter charts in OAM project (See OAM.git "solution-k8s" - & reach out to Alex Dehn 

    • https://gerrit.o-ran-sc.org/r/gitweb?p=oam.git;a=tree;f=solution_k8s 

• Need to pull latest version of A1 Policy functions from ONAP - good few updates since Oslo release

SIM (@Alex Stancu)

• No Update this week: See previous weeks

OAM (@Martin Skorupski)

• Updating to latest specs from O-RAN

• Updating Release L wiki page

AI/ML platform project (@subhash)

• Minutes & Meeting: Meeting notes

• Calendar: https://lists.o-ran-sc.org/g/main/calendar

• No Update this week

SMO (@Seshu Kumar Mudiganti)

• Meeting notes Meeting notes

• No specific update

• Topology & Inventory: (@John Keeney (Ericsson EST) :

  • Lots of small updates in K-Release & ongoing. Focus on ingestion adapters in this release.

OSC Integration / INT (@fransiscus bimo )

• Minutes: https://lf-o-ran-sc.atlassian.net/wiki/display/IAT/Current+Meetings

• Looking at contributing about Intent Management

  • Requires a capability store to describe rApp capailities

    • Service/API Registry from SME in NonRTRIC? 

      • @John Keeney (Ericsson EST) - Really only for APIs - doesn't really describe capabilities in a way usefull for Intent Management 

        • e.g. "SupportedFeatures" SME/Capif response - but that field is specific for a single exposure. Bit mask field - so likely is not a plain test string that could be reused.

        • e.g. in TEIV - again unlikely to be useful, since TEIV data model is specifically targeting topology (with yang extension)

        • e.g. in rApp Manager - but this is only for rApps then - cannot capture capabilites for other services, e.g. SMOSs

        • So might need a dedicated capability store? (Some advantages to using a semantic/RDF store ...? Or maybe CPS if yang based data? )  - depends on type/format of data

Meeting ends 50min