2023-08-08 Meeting notes (ONAP/O-RAN-SC/SMO - Meeting) - Agenda

John Keeney

Please follow the calendar

• https://lists.o-ran-sc.org/g/main/calendar

• https://lists.onap.org/g/onap-meetings/calendar# 

• 2023-08-15 John Keeney 
• 2023-08-22 Martin Skorupski
• 2023-08-29 John Keeney 
• 2023-09-05 Martin Skorupski

• O-RAN-SC ToC

• • https://wiki.o-ran-sc.org/display/TOC#ORANSCTechnicalOversightCommittee(TOC) 
    • OSFG O-RAN-SC OAI collaboration 
    • OSFG O-RAN-SC ONF collaboration 
      • Use Case: Energy Saving

• Non-RT-RIC: John Keeney 

• • plans for maintenance release
    • run PM functions
  • Please see:  https://wiki.o-ran-sc.org/display/REL/H+Release#HRelease-Non-Real-timeRIC(NONRTRIC)
  • Still wrapping up last bits of documentation (OSC & ONAP)
  • RAN PM functions - tidying up & re-releasing in maintenance release.
    • May impact AIMLFW project: Will discuss with Joseph Thaliath 
  • Making good progress on rApp manager. start and stop operations
  • 3GPP dependency updates & addressing vulnerability
  • Some changes in A1-Mediator in near-RT-RIC plt in H-Release.
    • Further investigation needed;  effects on A1-PMS & A1-SIM

• SIM: Alex Stancu
  • no plans for maintenance release
  • I-release planning
    • RASC: O2 API Sim???

• OAM: Martin Skorupski
  • no plans for maintenance release
  • yang-schema-mount support RFC8528 as required by O1 WG5 
  • Definition of PM streaming 
• O-DU: @Vidhu
  • no report

• AI/ML: @Joseph Thaliath

  • Minutes & Meeting: Meeting notes 

  • analysing specs for I -Release 
  • H-Release maintenance - some minor issue
  • I-Release planning ongoing

• SMO: Seshu Kumar Mudiganti 
  • Minutes & Meeting: Meeting notes 
  • I-Release → different orchestration - looking for contributions and resource commitments 
• INT: James Li(CMTI)
  • H-release - see https://wiki.o-ran-sc.org/display/TOC/TOC+Documents
  • no plans for maintenance release
  • O-RAN-Alliance - CEAG - takes care about O-RAN-SC press releases too
  • pair wise testing ongoing

N.K. Shankaranarayanan 

SDN-R interfacing with Configuration & Persistency Service

• to be updated the page was created 3 years ago
• Martin Skorupski : Provide info about yang-capabilities exposed by SDN-R.

N.K. Shankaranarayanan 

N.K. Shankaranarayanan 

• ONAP SON uses case ... & others
  • Coming together well now. ... counting down to M3
  •  See links below:
    
    • https://wiki.onap.org/display/DW/O1+CM+Update+Notification+VES+Message
    • https://wiki.onap.org/display/DW/CPS-1434%3A+VES+Message+to+update+CPS+DB
    • https://jira.onap.org/browse/CPS-1434
    • https://jira.onap.org/browse/INT-2177
• Update
  • CPS - how the code can be used?
    • modification of yang (subset for needed use case) to be applied and
    • other configurations (dataset as json)
    • yangs can be also injected based on SDNC (NF yangs - in this case unmodified yangs)
    • manual steps vs automation
    • CPS demo:  2023-04-04 Meeting notes - Developer Wiki - Confluence (onap.org)
      
      • https://wiki.onap.org/download/attachments/162106197/20230404_son_call_cps_api_demo.mp4?version=1&modificationDate=1680624282435&api=v2 
      • https://wiki.onap.org/display/DW/2023-04-04+Meeting+notes

Issue when deployment with OOM:

• oom - strimzi > 
  • one option to reinstall strimzi 

Preparation for the next release

• enhancements of RAN SIM

To be on the agenda for June 13!

on the Agenda at O-RAN f2f on WED.

N.K. Shankaranarayanan Seshu Kumar Mudiganti John Keeney Martin Skorupski 

• N.K. Shankaranarayanan  Presentation of slides discussed in past weeks at RSAC call today. See above.
  
  • Draft Slides: (for presentation at RSAC)
    
    • 
  • Update: (14/06/2023)
    • Following presentation at RSAC

      •  using the term "scenario" instead of "use case"

      • red and blue colors for the names of projects/components in the figure

      • separate slide to capture SMO interaction scenario for ES use case

      • RSAC Recording/ minutes will appear here soon
      • Draft Slides:
        
  • Older ... 
    
    • https://wiki.o-ran-sc.org/download/attachments/3604609/ONAP_OSC_Areas_20230321.pdf?api=v2 
    • Based on discussion of topics on : https://wiki.onap.org/pages/viewpage.action?pageId=162105284 
    • Recording: (second half of) https://zoom.us/rec/share/D3ZkRsAQ1lu9QY1zomJmAnmXzAUL3FTWJSFqCPDIUKVmZ96HbEu7DQLy34yidjDe.GMyDeZXm34UwgOSR
  • Excellent session to make people aware / motivated about overlaps, with concrete opportunity for better alignment & engagement.
• Seshu Kumar Mudiganti We also need to concentrate on Non functional aspects, such as scalability, security, energy usage. John Keeney Those are costly. Trade off against resources available for functional aspects. Do we need to find out if there is a preference for functional vs non-functional?
• Lots of hard work to do. We will try to identify concrete follow ups.
• Lets continue on the areas we already have good alignment, & strengthen focus on newer potential areas, as described int he slides.

N.K. Shankaranarayanan 

Still! "not ok" - how to use NETCONF YANGs from 3GPP and O-RAN

Problem Statement might be not fully understood. 

Next step: Call with Magnus Buhrgard 

After the call and some emails: Magnus it preparing a call with 3GPP SA5 representatives and then another ONAP LS to 3GPP

The topic is on the ONAP TSC agenda tomorrow: TSC 2022-09-08

• Update from Magnus Buhrgard at ONAP TSC call tomorrow
• Slides available

> Magnus wont give up