Time & Location:

Date

31 Mar 2021

Attendees

• John Keeney
• Martin Skorupski
• Alex Stancu
• Damian Nowak
• HariomGupta(HCL
• Kamel Idir
• Kenny Paul
• Konrad Bańka
• Marcin Krasowski
• Marcin Wilk
• Pawel Slowikowski
• Sonia Sangari
• Timo Perala
• Vidhu Shekhar Pandey
• Zu Qiang (Ericsson)
• Some others may have joined later ... please add yourself

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

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

Contents:

Recording

• Recording (cloud)
• Recording (low res mp4)

Notes:

Housekeeping:

• Timezone management
  • 2021-03-31    | 9am PDT |  noon EDT | 16:00 UTC | 17:00 BST | 18:00 CEST | 21:30 IST | 23:00 CST | 00:00 JST (Thurs)
  • 2021-04-07    | 9am PDT |  noon EDT | 16:00 UTC | 17:00 BST | 18:00 CEST | 21:30 IST | 23:00 CST | 00:00 JST (Thurs)
  • Calendars Updated - Please check in your timezone!
    
    • https://lists.onap.org/g/onap-meetings/calendar
    • https://lists.o-ran-sc.org/g/main/calendar
      
      
• Reminder from previous weeks:
  • OSC SMO calls now move to its own time slot - Thursdays
  • See OSC RSAC Calendar: https://wiki.o-ran-sc.org/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:

NONRTRIC (John Keeney)

• CII badging: CII status: NONRTRIC & https://bestpractices.coreinfrastructure.org/en/projects/4611 PASSED
• Updating a bug in ONAP OOM for A1 Policy functions - supporting Dan T - PTL
• A1 Policy functions in ONAP: ONAP Istanbul Requirement Approved (REQ to follow)
• Not alot of other progress this week - most of the team on training course.

SIM (Alex Stancu)

• O-RU / O-DU-Hello-World integration implementation ongoing for use case.
• Confirm ODL Silicon works with Simulators

OAM (Martin Skorupski)

• New Slack Channel:  #ccsdk-sdnc-features
• Updating Docker Compose file for OSC to include OAM functions https://gerrit.o-ran-sc.org/r/gitweb?p=oam.git;a=blob;f=solution/integration/smo/docker-compose.yml.
  • version updates etc (SDNC, VES, DMaaP)
    
  • Current version https://gerrit.o-ran-sc.org/r/gitweb?p=oam.git;a=blob;f=solution/integration/smo/docker-compose.yml
• Docker Compose for NONRTRIC functions?
  • Include in One file or have multiple
  • Will investigate this week offline.
• Working on identity server - Keycloak
• ODL Silicon
• Test docker compose for whole use case.

ONAP - OSC:

• Discussion at ONAP TSC about OSC/ONAP/O-RAN collaboration/alignment Swaminathan Seetharaman Martin Skorupski John Keeney

  • https://wiki.onap.org/display/Meetings/TSC+2021-03-25
  • Slides:
    
  • Suggestions:
    • More formal alignment process between OSC & ONAP & ORAN Alliance
    • Discussion around cross-project requirements, usecases, timelines & release cadences, points of contact.
  • Outcomes
  • Very positive feedback
  • Meeting organized between ONAP TSC & OSC TOC co-chairs & Linux Foundation
    
    • No update from this meeting yet. Watch TOC calls in coming weeks.

• Damian Nowak Any udate about O2?
  • Martin Skorupski Draft version Information Model from WG6 - very draft-ey & under discussion

• A1 Proxy: Hieu Nguyen - Has left Samsung, and unlikely to continue this work
  
  • Pawel Slowikowski Any update for using Kong?
    • John Keeney Unclear the need - instead want to handle a 3rd party proxy below the A1 adapter
  • John Keeney Kong as an approach for isolating functions in ONAP sounds useful in general though.
  • John Keeney Should come up with a picture/page describing this topics. (Action)

• Pawel Slowikowski Feedback Notification for A1 Policies.
  • Where is the endpoint for receiving notifications
  • John Keeney Currently we don't have a requirement for how to use the feedback. Simplest option - which we use - is the feedback goes direct to the policy creator - bypassing the A1-PMS
  • Also considering having A1-PMS acting as an aggregator for this feedback. But we do not want policy-type-specific functionality in the A1-PMS. But currently feedback is policy-type-specific.
  • Pawel Slowikowski Is it spec compliant wrt feedback?
    • John Keeney Yes. Definitely. There is nothing in the spec to say where feedback goes or how it is handled.
  • John Keeney We use a simple common feedback/notification receiver function in our demos etc.
  • Currently we have no use case or requirement for anything more sophisicated yet.
  • Ref also question from Krystian Kedron on slack https://onapproject.slack.com/archives/C01K8CNUJA2/p1617110362003600  John Keeney Apologies for missing this on slack.
  • Usecase?
    • John Keeney Could be useful for UE-specific policies where UE moves between near-rt-rics. One useful notification would be that the UE-specific policy is non-enforceable so needs to move?
  • John Keeney Very much welcome community feedback here.
  • Pawel Slowikowski Note Samsung uploaded use case to ONAP INT. Might be useful use case for notifications?