Page History

...

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

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

Contents:

Recording

• Recording (MP4)

Notes:

• Happy New Year!
  

• Meeting 16 December cancelled due to holidays
• Meeting 23 December cancelled due to holidays
• Meeting 30 December cancelled due to holidays
• This meeting: 06 January 2021
• Next meeting: 13 20 January 2021Short meeting due to small attendance & vacation day in most of Europe.

• Apologies for the confusion joining the call bridge. (Bridge was reconfigured to add a password)
• Please us the new updated Zoom (above) next week also! (Invites etc have been updated)

OSC Project roundup

• OSC Cherry Release Completed - Press release ongoingO-RAN (O-RAN-SC) Press release for "Cherry"-Release

NONRTRIC (John Keeney)

• Maintenance release: No major update - Just back from vacation. Looking forward to a busy year!

SMO

• functional change envisioned - most small changed & documentation
  
  • Examining which functions to cherry pick from master→cherry
• Dawn requirements planning ongoing
  • Mostly evolution of Cherry functions
  • Beginning to examine rApp platform & packaging - and overlap with "common app" activities
  • Also continuing to look at requirements for R1
• ONAP Honolulu (A1 Policy functions)
  • Incremental evolution continues

SMO (Mahesh Jethanandani )

• No update - need to confirm with Mahesh Jethanandani if this time is suitable.No update

SIM (Alex Stancu)

• No major update
  • All OSC projects need to look at CII badging questions - ref toc 06/01/2020  https://wiki.o-ran-sc.org/display/TOC -
    • See Core Infrastructure Initiative (CII) Badging in OSC.

OAM (Martin Skorupski)

• Continuing to work on IPV6 support (Ref Image RemovedSDNC-895) - mainly problem connecting from ODL to other ONAP components.
  
• Continuing to study ODL Aluminium version usage ONAP (SR1 vs SR2). E.g. see https://jira.opendaylight.org/browse/NETCONF-744 Will discuss with Dan Timnony.

ONAP - OSC

• Swaminathan Seetharaman will report to ONAP TSC ... any additional input reqd.?

  • John Keeney Perhaps request TSC to reach out to OSC TOC & RSAC committees to help drive the alignment forward.
    
    • Swaminathan Seetharaman John Keeney Which concrete touch points would be good to drive this leadership-level discussion:
      • existing ONAP usecases (see Potential ONAP <-> O-RAN collaboration use cases)
      • OSC-SMO/NONRTRIC/OAM overlap,
      • ONAP Slicing (especially wrt ORAN-Alliance use case overlap)
      • New usecases?
  • Martin Skorupski It would be good to understand timelines/dates/cadences between ONAP & OSC to help clarify when/how requirements/releases in both projects depend on each other.
  • Martin Skorupski Yang copyright alignment & spec re-use remains a challenge ....
• Andy Mayer ONAP modelling for O-RAN ... Will follow up in coming weeks (next week?).

• No plans for Cherry Mantenance Release
• Please see Release C press release (above).
• Will continue discussions on new end-to-end "control loop" use case with RSAC.
  
  • John Keeney Martin Skorupski Current O-RU recovery has no A1 aspect, and adding A1 would be challenging. Can use the usecase as a requirements-driving usecase for a simple rApp instead.

ONAP - OSC

Latest update from ONAP Modelling Andy Mayer 

• (Video @ 00:08:00 in recording) 
• Wiki page https://wiki.onap.org/display/DW/ONAP+Information+Model+-+Clean+and+approved+models+across+ONAP+releases
  • Has latest updates & landing page - "Clean" versions
    • e.g. Ves 7.2 update for CM notifications etc
  • ONAP modelling subcommittee: https://wiki.onap.org/display/DW/Modeling+sub-committee 
    • Current activities tracked at https://wiki.onap.org/display/DW/Modeling+Current+Activity+Status
    • Backlog etc: https://wiki.onap.org/pages/viewpage.action?pageId=84669119
• Martin Skorupski Note new O-RAN Alliance new Workgroups "WG10" to handle OAM activities
  • Including O1 & M-Plane (Partly driven by 3GPP for O1 and IETF (OFH) for M-Plane)
• Andy Mayer - How does O-RAN SMO map to ONAP?
  • Martin SkorupskiJohn Keeney Not directly - very little detail in O-RAN documents - mainly requirements for SMO in Architecture & usecases. However Non-RT-RIC is being defined, as part of SMO, but it remains unclear what is a functional architecture for SMO. 
  • Andy Mayer Maybe we should try document some assumptions/requirements for SMO to help steer ONAP.
    • John Keeney OSC SMO/OAM/NONRTRIC should help here. Andy Mayer but O-RAN Alliance should drive requirements etc ....
• @? Which 3GPP release forms basis for OAM models? R17?
  • R16.5 seems to be the basis. Ongoing study & input needed to identify updates in versions.

ONAP Usecases Update

• Swaminathan Seetharaman could not attend.

Other

• Michela Bevilacqua Can we invite someone to describe the new WG10 OAM workgroup?
  
  • Martin Skorupski Still being setup .... Also discussion will happen at vF2F
    • https://oranalliance.atlassian.net/wiki/spaces/OAH/pages/1303937147/Virtual+F2F+Meetings+January+25+-+February+5+2021
    • Will come back with more details when we know more.

• Michela Bevilacqua Would be good to have a O-RAN-related meeting at LFN-DDF meeting?
  • Martin Skorupski John Keeney Swaminathan Seetharaman Proposal avaialbe at https://wiki.lfnetworking.org/display/LN/2021+February+Developer+Topic+Proposals#id-2021FebruaryDeveloperTopicProposals-ONAP/O-RAN/OSCAlignment-UpdatesandRoadmap
  • John Keeney Also an O-RAN vF2F - should try have some discussion there too?

• Lasse Kaihlavirta O-Cloud.  Will reference implementation be done in OSC?
  • John Keeney Martin Skorupski Possibly the INF project? Infrastructure Home Xiaohua Zhang
  • Lasse Kaihlavirta Interfaces still being defined. Any plans for simulators? e.g. O2 simulator? ... Not sure. Will check with RSAC.

• Konrad Bańka Rest based config of A1-PMS. Currently tested & working ... Will it be added in ONAP-Guilin-Maintenance-Release?
  • John Keeney In OSC Cherry ... Will check with team if t will be cherry-picked back to maintenance release

Apologies again for the mix up with the bridge password etc.

...