2023-05-10 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-05-10 Martin Skorupski  (jk ooo)
• 2023-05-17 John Keeney
• 2023-05-24 Martin Skorupski 
• 2023-05-31 John Keeney

• O-RAN-SC ToC

• • https://wiki.o-ran-sc.org/display/TOC#ORANSCTechnicalOversightCommittee(TOC)
    • ToC reports - see https://wiki.o-ran-sc.org/display/TOC/TOC+Documents
    • this week: Non-RT-RIC and SMO

• Non-RT-RIC: John Keeney 

• • Made progress on how to have multiple project in single repo.
    • Change conf.py & .readthedoc.yaml: https://gerrit.o-ran-sc.org/r/c/nonrtric/plt/ranpm/+/10991 
  • Documenting & improving how to deploy RANPM functions. Will demo again in coming weeks
    
    • AIMLFW had some issues & questions. Working on those.
  • Will push on with work on rApp manager - especially rApp onboarding, preparing for SME, DME etc
    • Lots of bits there already ... this will tie them together in a coordinated way when deploying rApps
    • Much of the rAPP LCM will be handled by ONAP ACM functions
    • Main issue is we still have no clear definition of rApp package.
    • We will likely be out of alignment with O_RAN specs when they arrive / mature. We will evolve our work then.
  • Will demo Service Registry & Service Discovery - based on CAPIF
    • Working now. 
  • Will demo ONAP SO CNFM function for ASD-packages CNFs deployment - working in standalone mode.
    • We've removed dependency on SDC and A&AI - replaced with initial stub functions.
    • So CNFM in standalone mode gives ASD deployment support - either on its own or as part of a larger ONAP SO/SDC/A&AI install.
    • Propose to demo at joint SMO/SO call, maybe 2 weeks? Or RSAC call in 2 weeks. 
  • Continuing as per last week :
    
    • Alot of work in JDK 17 & Springboot 3 updates
    • Consolidating PM data exposure in new repo for RAN PM functions
      • https://gerrit.o-ran-sc.org/r/gitweb?p=nonrtric%2Fplt%2Franpm.git;a=summary
    • (R1) Service Exposure & Management
      • CAPIF Aligned Service Registry
      • Secured/Sandbox execution environment
      • Controlled access & exposure of service to/from rApps
      • 2023-04-19: good progress - maybe a demo in a couple of weeks.

    • (R1) Data Management & Exposure

      • File-based PM data → InfluxDB
      • Previous focus on PM data - but will extend to other use cases too
      • Aim to work with AIML project for Training (and Inference ?) data access

    • rApp Management

      • Built on ONAP “Automation Composition” model & platform to implement rApp use cases
        • Inference Services in rApps
          • Added a 'KServe Participant'
        • rApp-specific extensions needed
      • Packaging, Onboarding & Orchestration of rApps
        • rApp-specific packaging & Onboarding
          • Aim to align with / inform ongoing work in O-RAN (& OSC) about Common App packaging & Onboarding.
        • (rApps with & without µService)
      • Overlap with Service Exposure work to examine role of an rApp Manager to support controlled exposure & LCM of µService and non-µService parts of an rApp

    • Continued A1-Policy & A1-Enrichment-Information evolution (& R1-A1)

      • A1 Spec evolution
      • A1-Policy work in ONAP (continues in ONAP London) - candidate for R1-A1(P)
      • A1-EI management as part of DME - candidate for how to include A1-EI in R1-DME
      • 2023-04-19: fine grain access control
    • Sample use cases (rApps)
      • Requirements Drivers for rApp/R1 development
      • High degree of cross-project integration activity

    • Testing, Maintenance & Housekeeping

      • Function Test & Integration Test environment,
      • Support integration, deployment & configuration of SMO/Non-RT-RIC related functions & usecases in OSC Integration env.
      • Project coordination, Documentation, Delivery, Reporting, Cross-project alignment, Community demos, O-RAN Standardization support, etc.
      • test deployments
    • Demo in RSAC - May17
      • CAPIF Aligned Service Registry (pre-rApp-Manager )
      • CNFM  
    • Maybe demos also in the SMO call May24 - video

• SIM: Alex Stancu
  • PM File generation
    • update for the stndDefined fileReady → 3GPP REL-18
    • John Keeney Alex Stancu : req: file ready event - template for 3gpp-xml file → timestamps - generated provided by John
      • same certs for FTPes 
      • each sim instance will create its own file (file per node)

• OAM: Martin Skorupski
  • release notes - issue with docx
  • Current version deployed as docker-compose in COSMOS.
  • Simplified (docker) networking
• O-DU: @Vidhu
  • no report

• AI/ML: @Joseph Thaliath
  • int scripts  

  • Minutes & Meeting: Meeting notes

• SMO: Seshu Kumar Mudiganti 
  • working on logistics
  • merger of ONAP SO and O-RAN-SC SMO
  • separation for business logic and deployment
  • SMO disaggregation on next weeks agenda - same as RSAC meeting
  • working with nephio - for integration with O-RAN Specs
    • slot in nephio project 
  • time changes: one hour later - new bridge
  • Tacker flows were reviewed and understood and are on track.

            Orchestration

• • • • INF and SMO O2 service: for O2 IMS inventory (including O-Cloud Registration or O-Cloud Available Notification), and query O2 DMS endpoints of the O-Cloud
      • INF and SMO Tacker: for tacker to orchestrate vCU/vDU to O-Cloud (which has been done since F release)

Platform

• • • • SMO O2 service and RIC-Platform: to forward the O2 DMS endpoints of the O-Cloud
      • SMO O2 service and SMO tacker: to forward the O2 DMS endpoints of the O-Cloud 
• INT: James Li(CMTI)
  • h-release - see https://wiki.o-ran-sc.org/display/TOC/TOC+Documents
  • no report

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 

Planning ahead

• What happens with O-RAN-SC? ... and all the "overlaps" in context of O2/O-Cloud
• use cases:
  • flow: app / O1 / O2 / A1 / E2 (depending on Near-RT-RIC function) 
  • e.g. cNF deployment  according defined flows 
  • helps the discussion going forward

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.
  
  • Slides: 
    
    • 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