2021-03-31 Meeting notes (ONAP/O-RAN-SC/SMO - Meeting)

Owned by Martin Skorupski
Last updated: Apr 07, 2021 by John Keeney (Ericsson EST)
3 min read

 | 9am PDT |  noon EDT | 16:00 UTC | 18:00 CEST | 21:30 IST 

Note:

  • North American daylight saving 2021 starts March14
  • European           daylight savings 2021starts March28


ZOOM:https://us02web.zoom.us/j/89069708424?pwd=aGJOZm54eTUxd0FXR0VCU1N0ejBrUT09
Meeting ID: 890 6970 8424

Attendees

Informed

Please add/remove yourself. Thanks!

See also


Goals

  • share information between
    • O-RAN-SC Non-RT-RIC
    • O-RAN-SC OAM
    • O-RAN-SC SMO
    • ONAP CCSDK/SDNC/SDN-R
    • LFN (wink)

Recording

Discussion items

TimeItemWhoNotes
00:00Admin

Martin Skorupski

Next meetings: 

2021-04-07: John Keeney (Ericsson EST)

2021-04-14: Martin Skorupski   -

2021-04-21: John Keeney (Ericsson EST)

2021-04-28: Martin Skorupski

00:05O-RAN-SCO-RAN-SC PTLs

Status reports:

  • Non-RT-RIC: John Keeney (Ericsson EST) 
    • supporting Dan
  • SIM: Alex Stancu  
    • O-RU and O-DU-hello-world under implementation
  • OAM: Martin Skorupski
    • yet another slack (wink) #ccsdk-sdnc-features
    • Update docker-compose (link)
      • to onap-sdnc:2.1.3 (version from Mar26)
      • to org.onap.dcaegen2.collectors.ves.vescollector:1.9.0
      • to DMaaP - 1.1.18
    • next steps
      • integration of an identity server
      • update ccsdk to ODL silicon - needed for NETCONF-Call-Home/TLS
      • creation of a use case specific docker-compose with simulated O-RU-Fronthaul and O-DU-hello-world.yang + ves:pnfRegistration (maybe ves:heartbeat, ves:fault) - header VES:7.2.1
00:10SMO functionality and alignment between ONAP and O-RAN SC

Swaminathan Seetharaman

SMO functionality and alignment between ONAP and O-RAN SC

  • Swami, John and Martin: slide set was presented 
  • There was a meeting between ONAP TSC and O-RAN-SC ToC - including LFN
00:15

Q/A



00:15Scope of this call

damian.nowak

SMO

  • O-RAN O1 - covered here
  • O-RAN A1 - covered here
  • O-RAN O2 → How to address it? Waiting for first version of the spec. → O-RAN WG6
00:16"A1 Proxy"Hieu Nguyen

Proxy between A1-Adatper and Near-RT-RIC

  • ULRs
  • Certs
00:16"A1 Proxy"Pawel Slowikowski

more on A1 Proxy

  • internal Proxy → 2 proxies in a row
  • maybe a wiki helps also in future
00:20Architecture

Pawel Slowikowski

Feedback notification to Policy

  • Policy vs Analytics - where to implement?
  • Issue no use case driving this topic yet
  • Spec says - notification yes, but not info about its processing
  • Notification receiver - currently logs the notification

from Slack:

Hi O-RAN-ONAP experts!
I have one question regarding the feedback policy operation, do you plan (or have some idea) how this operation should be supported in ONAP (as an SMO)?

Answer: We have a plan - but there are several options and it is not clear which one to choose

follow-up question: What should be done with such notifications? 

potential use case: UE movement → clean up of Policies when moving from one Near-RT-RIC to the next

Currently, we have only the status_notification_uri field in the policy preload available. But the http server is missing on the A1-P Consumer site (ONAP-PMS, SDNC/A1 Adapter) that will respond to this POST request (feedback) from the Near RT RIC site.

How is the community vision on this topic? I wonder that this "feedback" should be handler by R-APPs or the PMS will be responsible for that?

Answer: might be use case driven

I saw that the community not use this slack channel but this is my first attempt to start some discussion here. Also this topic can be handler during our weekly call 

we will be better (wink)

END






00:??Use Case

@all

OSC Proposed e2e integration use case: O-RU FH connection recovery

<bridge dropped recording stopped at this point. Most participants reconnected once bridge started again>



Action items