Time & Location:

Date

Oct 6, 2021

Attendees

• @John Keeney (Ericsson EST)

• @Martin Skorupski

• @Alex Stancu

• Arnold Alvarado (NIWC Pacific)

• Christophe Closset (AT&T)

• @David Johnson

• Douglass Evans (USN)

• Fernando (Fred) Oliveira (Verizon)

• @Hariom Gupta

• Ioui Raspberry

• Janak Kulkarni

• @Kamel Idir

• @Kevin Tang

• @marcin krasowski

• Marcin Wilk

• Martial Ngueko (AT&T)

• @michal.cmarada@gmail.com

• @N.K. Shankaranarayanan

• @Pawel Slowikowski

• Pawan Kumar

• Ryan McAllister

• Sebastien Determe (AT&T)

• @Sonia Sangari

• @Timo Perala (Nokia)

• @Tracy Van Brakle

• @Vidhu (Deactivated)

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

• Co-located with ONAP 2021-10-06 Meeting notes (ONAP/O-RAN-SC/SMO - Meeting)

Contents

Recording

Notes:

Housekeeping:

OSC SMO Meeting Series: Reminder from previous weeks:

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

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

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

OSC Project roundup:

News from OSC TOC call this week

• https://lf-o-ran-sc.atlassian.net/wiki/display/TOC/

• M3 deadline extended .. 3 weeks? Perhaps combine M3 & M4?

• Processes to support SCCL license is still ongoing & under discussion

  • https://www.o-ran.org/sccl

• For E Release Slicing Assurance use case ... Can we use 3GPP yang models for O-DU OAM?

  • Unclear

  • Still have backup "Plan B" to reuse/extend "Hello World" model from D release

NONRTRIC (@John Keeney (Ericsson EST))

• No update this week

SIM (@Alex Stancu)

• TLS call home now working in SIM (ODL Silicon+ )

  • (Bug? SSH Netconf callback connections drop after 10 minutes if no messages)

OAM (@Martin Skorupski)

• Creating "Plan B" yang model for slicing use case (see above)

• Working on WG10 CR for PM streaming (+ @N.K. Shankaranarayanan @David Kinsey [AT&T] )

  • Timelines too tight for November train ... Will continue in next train

O-DU (@Hariom Gupta (Deactivated))

• @Vidhu (Deactivated) Still blocked re Yang model decisions

Using 3GPP models 

• Discussion: @Martin Skorupski @Timo Perala (Nokia) @N.K. Shankaranarayanan @John Keeney (Ericsson EST)

  • Still a lack of clarity about how to use 3GPP licensed models

  • Approach until now has been to stay model-driven (so don't reproduce any existing specs/models)

    • But this cannot continue esp. in OSC when O1 builds so much on 3GPP specs and functions that are model-specific are now in development.

  • Is problem for ONAP & OSC the same?

    • Yes!

    • Perhaps we could escalate to LF?

      • @Timo Perala (Nokia) - Can raise at ONAP TSC & maybe include @Kenny Paul (Deactivated) to see if ONAP can ask LF legal can help?

ONAP SMO deployment options

• Christophe: Working with @David Johnson to reuse ONAP/OSC SMO deployment/package in POWDER lab as a profile

  • Working setup now. Tweaking configurations to reduce footprint size a little for smaller deployments

• Next step - aiming for meaningful automated end-to-end tests

Q&A

• Pawan Kumar, Janak Kulkarni: New to OSC/ONAP integration & interested in getting up to speed   (Welcome!!! )

  • How's progress with rApps & R1?

    • @John Keeney (Ericsson EST) Neither are very well defined yet ... but in OSC & ONAP we are trying to guess at some of the parts that will eventually be useful for supporting R1 & rApps ...

      • App LCM

      • uService LCM & management (for rApps with microservices)

      • ONAP Tosc-defined Control Loop evolution (for rApps with multiple constituent parts including non-microservice parts, e.g. policies, workflows, configurations, templates, blueprints, etc)

      • ONAP SMO services - which may become/inform R1 services (e.g. CPS, Data collection, File collection, VES termination, Topology & inventory, Orchestration etc)

      • Service exposure & discovery & authorization & access control (which will likely be useful for R1 - service independent)

      • App sandboxing & controlling App <-> SMO interactions (which will likely be useful for R1 enforcement)

      • etc ...

  • Attempting to get ONAP & NonRTRIC & nearRTRIC functions running

    • @John Keeney (Ericsson EST) Please check out the wiki pages for details on how to run the functions, & any issues please use the mailing lists discuss@lists.o-ran-sc.org & onap-discuss@lists.onap.org is you have any issues.