2023-05-03 Meeting notes - Joint OAM / NONRTRIC / SIM Community meeting

2023-05-03 Meeting notes - Joint OAM / NONRTRIC / SIM Community meeting

Time & Location:

Meeting Detail: Times & Joining Info

Wednesdays at 16:00 UTC in Summer, 17:00 UTC in Winter!

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

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

  • Meeting ID: 890 6970 8424.

  • See the 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 Daylight Savings time eventually stabilizes to:

      9am PDT | 12pm EDT | 16:00 UTC | 17:00 BST | 18:00 CEST | 19:00 EEST | 21:30 IST | 00:00 CST (Thurs) | 01:00 JST (Thurs)

    • Winter (non-DST) time eventually stabilizes to:
      9am PST | 12pm EST | 17:00 UTC | 17:00 GMT | 18:00 CET | 19:00 EET | 22:30 IST | 01:00 CST (Thurs) | 02:00 JST (Thurs)

    • (During Winter→Summer DST changeover follow US time. Summer→Winter DST changeover follow Europe time

Please checkout the calendars:

Anti-Trust Notice

Date

May 3, 2023

Attendees

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

  • @Martin Skorupski (Highstreet & OSC OAM)

  • @Alex Stancu (Highstreet & OSC SIM)

  • @James Li (CMTI & OSC INT)

  • @Seshu Kumar Mudiganti (Wind River & OSC SMO)

  • @N.K. Shankaranarayanan (ONAP)

  • @Aravindhan Ayyanathan (Ericsson EST)

  • @Kevin Timoney (Ericsson EST)

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

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

Contents

Recording

Notes:

Housekeeping:

Should we change the time for this call?

  • Best suggestion is Tuesdays at 14:00 UTC.

    • If no objections in coming week we will propose to change.

    • What time where you are?

    • Tuesdays: 7am PDT | 10am EDT | 14:00 UTC | 15:00 BST | 16:00 CEST | 17:00 EEST | 19:30 IST | 22:00 CST | 23:00 JST 

OSC Project roundup:

News from OSC TOC call last week

NONRTRIC (@John Keeney (Ericsson EST))

  • Made progress on how to have multiple project in single repo.

  • Documenting & improving how to deploy RANPM funcions. Will demo again in coming weeks @Björn Magnusson 

    • @Joseph Thaliath in AIMLFW had soem issues & questions. Working on those.

  • Will push on with work on rApp manager - especially rApp onboarding, preparing for SME, DME etc

    • Lots of bits there already ... this will tie them together in a coordianted way when deploying rApps

    • Much of the rAPP LCM will be handled by ONAP ACM functions

    • Main issue is we still have no clear definition of rApp package.

    • We will likely be out of alignment with O_RAN specs when they arrive / mature. We will evolve our work then.

  • Will demo Service Registry & Service Discovery - based on CAPIF

    • Working now. @Yennifer Chacon 

  • Will demo ONAP SO CNFM function for ASD-pacakaged CNFs deployment - working in standalone mode.

    • We've removed dependency on SDC and A&AI - replaced with initial stub functions.

    • So CNFM in standalone mode gives ASD deployment support - either on its own or as part of a larger ONAP SO/SDC/A&AI install.

    • Propose to demo at joint SMO/SO call, maybe 2 weeks? Or RSAC call in 2 weeks. @Aravindhan Ayyanathan 

  • Otherwise continuing as per last week :

    • Consolidating PM data exposure in new repo for RAN PM functions

    • (R1) Service Exposure & Management

      • CAPIF Aligned Service Registry

      • Secured/Sandbox execution environment

      • Controlled access & exposure of service to/from rApps

    • (R1) Data Management & Exposure

      • File-based PM data → InfluxDB

      • Previous focus on PM data - but will extend to other use cases too

      • Aim to work with AIML project for Training (and Inference ?) data access

    • rApp Management

      • Built on ONAP “Automation Composition” model & platform to implement rApp use cases

        • Inference Services in rApps

          • Added a 'KServe Participant'

        • rApp-specific extensions needed

      • Packaging, Onboarding & Orchestration of rApps

        • rApp-specific packaging & Onboarding

          • Aim to align with / inform ongoing work in O-RAN (& OSC) about Common App packaging & Onboarding.

        • (rApps with & without µService)

      • Overlap with Service Exposure work to examine role of an rApp Manager to support controlled exposure & LCM of µService and non-µService parts of an rApp

    • Continued A1-Policy & A1-Enrichment-Information evolution (& R1-A1)

      • A1 Spec evolution

      • A1-Policy work in ONAP (continues in ONAP London) - candidate for R1-A1(P)

      • A1-EI management as part of DME - candidate for how to include A1-EI in R1-DME

    • Sample use cases (rApps)

      • Requirements Drivers for rApp/R1 development

      • High degree of cross-project integration activity

    • Testing, Maintenance & Housekeeping

      • Function Test & Integration Test environment,

      • Support integration, deployment & configuration of SMO/Non-RT-RIC related functions & usecases in OSC Integration env.

      • Project coordination, Documentation, Delivery, Reporting, Cross-project alignment, Community demos, O-RAN Standardization support, etc.

SIM (@Alex Stancu)

OAM (@Martin Skorupski)

  • Looking at OFH certification specifications

O-DU @Vidhu (Deactivated))

  • No update

  • Now will use new VES std-defined schema as discussed last week

OSC Integration / INT (@James Li )

  • Going through existing robot tests for near-rt-ric / xapps in it/test repo

    • Some incompatibilities in terms of how the platform is set up ... will work with near-rt-ric & xapp teams.

SMO (@Seshu Kumar Mudiganti )

  • Meeting notes for last week: 2023-04-26 Meeting notes

  • Next week: 2023-05-10 Meeting notes  

  • Working on logistics for SMO PTL tasks.

  • plan to merge ONAP SO & OSC SMO project meetings

    • Possibility of changing the meeting time?

  • Working on K8s Operator - especially how to separate business logic & deployment technology.

    • K8S Operator is now just a way to deploy, and can be deployed in other ways too.

    • Will soon demo updated version

  • Demo for K8s operator: (Will add link to the demo)

  • @Seshu Kumar Mudiganti requires access to groups.io calendar & info.yaml

    • May need help from @huangjinri@chinamobile.com or TOC mailing list

  • SMO disaggregation will be discussed at next SMO call.

  • Working on proposal of Nephio related SO work in Nephio blog

    • Will present same demo in Nephio too. (WIP)

RSAC (@David Kinsey [AT&T])

AI/ML platform project (@Joseph Thaliath)

ONAP Use cases (@N.K. Shankaranarayanan)

  • SON use: Issue: Then function deployment is by OOM it assume strimzi kafka, while dev teams assume plain kafka.

    • Plain kafka & Strimzi kafka are not directly compatible ...

    • Possible work around by reinstall strimzi?

ONAP / OSC / O-RAN Alliance: Cooperation & Alignment

  • No Update

Questions / Comments / AOB:

  • No time this week

 

Meeting ends 60min