2024-08-27 Meeting notes - Joint OAM / NONRTRIC / SIM Community meeting

2024-08-27 Meeting notes - Joint OAM / NONRTRIC / SIM Community meeting

Time & Location:

  • Time Change: This meeting is now 1 hour later - 15:00 UTC on Tuesdays

 

Meeting Detail: Times & Joining Info

Today: Tuesday at 15:00 UTC     (16:00 UTC in Winter Northern Hemisphere TBC)

https://us02web.zoom.us/j/89069708424?pwd=aGJOZm54eTUxd0FXR0VCU1N0ejBrUT09

  • Ensure you are signed into your Zoom account to join.

  • Meeting ID: 890 6970 8424. By Phone: Dial in (Local numbers): You will need a Participant ID so you will need to join the meeting from a Zoom client first to get this.

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

  • NOTE: During the "Daylight Savings Time" changeover periods (US vs Europe vs Asia) the time of the meetings may fluctuate. 

    • Summer (norther hemisphere) (Q2 & Q3) time eventually stabilizes to:
      8am PDT | 11am EDT | 15:00 UTC | 16:00 BST | 17:00 CEST | 18:00 EEST | 20:30 IST | 23:00 CST | +1d 00:00 JST (Wed)

    • Winter (non-DST) (Q1 & Q4): TBC: Probably 8am PST | 11pm EST | 16:00 UTC | 16:00 GMT | 17:00 CET | 18:00 EET | 21:30 IST | +1d 00:00 CST (Wed) | +1d 01:00 JST (Wed)

Please checkout the calendars:

Anti-Trust Notice

Date

Aug 27, 2024

Attendees

  • @John Keeney (Ericsson EST) (Ericsson EST & OSC NONRTRIC)

  • @Martin Skorupski (Highstreet & OSC OAM)

  • Subhash Kumar Singh (@subhash) (Samsung & OSC AIMLFW)

  • @N.K. Shankaranarayanan

  • @Aravindhan Ayyanathan (Ericsson EST)

  • @Francesco Davide Lapenta (Ericsson EST)

  • @Denis G Noonan (Ericsson Software Technology) (Ericsson EST)

  • @Simeon Wuthier (NIST)

  • Amir Arabi

  • @Varadarajan (Samsung)

  • @Deena Mukundan (Tech Mahindra)

  • Gururajaroa Bandalakunta (@guru raja) (Tech Mahindra)

  • Srinivas Yanamadala (Tech Mahindra)

  • 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)

Contents

Recording

Notes:

Housekeeping:

OSC Project roundup:

News from OSC TOC & OSFG calls last week

NONRTRIC (@John Keeney (Ericsson EST))

  • Still working away on issue from previous weeks:

    •  A1-Controller

      • NBI Issues: Last Week WG2 R1 spec for Nov release changes from March version (not backwards-compatible)Still trying to stabilise API for R1.

        • May cause disruption to users that have already adopted the New-Delhi or J-Release versions

      • Fixed a bug in A1-PMS in ONAP & OSC - Where 'transient' Policies were being deleted when a service is deleted.

        • Fix available & preparing tests & patch releases for ONAP (London, Montreal, New-Delhi) & OSC (J at least & hopefully older)

      • Fixing an issue with Service-ID (request param)  vs ClientID (in auth header) when creating an A1 Policy.

      • Updating to SpringBoot 3.3

      • Database-based persistent storage now enabled.

    • Service Manager

      • Hoping to discuss/demo (below) boot-strap service exposures at SMO start-up - but its proving a bit more difficult than expected.

      • Manual registration via API is still working fine - but currently all Services need to be explicitly registered rather than auto-registered.

    • Release K Planning:

      • No major update this week ... but will continue with more focus on demonstrators - esp aiming towards next F2F

SIM (@Alex Stancu)

  • Planning to demo Hybrid & Hierarchical OAM at F2f - including interesting issues like VES message translation.

OAM (@Martin Skorupski)

AI/ML platform project (@subhash )

OSC Integration / INT (@fransiscus bimo )

SMO (@Seshu Kumar Mudiganti)

RSAC (@Rittwik Jana  @Martin Skorupski )

Questions / Comments / AOB:

  • @Deena Mukundan

    • Question about CAPIF & Service Manager: How does an invoker update the list of Services/APIs it wants to invoke, after discovery.

      • @John Keeney (Ericsson EST) Current implementation assumes all Invokers (after registration) can discover all services. (Should be restricted to just the service they are allowed to invoke)

        • So currently, just go ahead and try access the service. Access to the service may then be locked by API Gateway of Service mesh, to enforce the Service Exposure.

        • CAPIF spec does not seem clear about how to do this.

      • @John Keeney (Ericsson EST) unlikely to work more on this in this release

        • Limited bandwidth

Meeting ends 27 min