Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Info
iconfalse

17:00 UTC, 09:00 PST, 12:00 EST,  17:00 GMT, 18:00 CET, 19:00 EET, 22:30 IST, 01:00 CST (Thurs), 02:00 JST (Thurs)


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


Calendars:

Summer Daylight Savings time eventually stabilizes to:
9am PDT | 12pm EDT | 16:00 UTC | 17:00 BST | 18:00 CEST | 19:00 EEST | 21:30 IST | 00:00 CST (Thurs) | 01:00 JST (Thurs)

Winter (non-DST) time eventually stabilizes to:
9am PST | 12pm EST | 17:00 UTC | 17:00 GMT | 18:00 CET | 19:00 EET | 22:30 IST | 01:00 CST (Thurs) | 02:00 JST (Thurs)

(During Winter→Summer DST changeover follow US time. Summer→Winter DST changeover follow Europe time)


Table of Contents

Table of Contents

Attendees

Informed

Discussion items

TimeItemWhoNotes
00:00Admin

Next meetings: 

2021-12-01: Martin Skorupski 
2021-12-08: John Keeney 
2021-12-15: Martin Skorupski  
2021-12-22: proposal: canceled John Keeney
2021-12-29: proposal: canceled
2022-01-05: proposal: canceled
2022-01-12: Martin Skorupski 

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

O-RAN-SC ToC


Projects:
  • Non-RT-RIC: John Keeney
    • working on rApp for the slicing use-case
    • open questions - e.g. slice id values 
    • focus on rApp "management" - life-cycle-management
  • SIM: Alex Stancu
    • working on the network-slicing use case
      • subscription to a VES stream
      • PM-Job management
      • Sending PM ves messages as "stndDefined"
      • CM for radio-resource-management per slice
      • CM du functions (Cell → slice)
  • OAM: Martin Skorupski
      working across several projects and O-RAN (preparation or March Train)
    • "validation" of the new NTSim functions as listed above
    • release note
  • O-DU:HariomGupta(HCL) / @Vidhu.  
    • cm (3GPP yang - rel17-draft)
    • pm in ves:measurement to O-RAN-SC-SMO
    • stabilize code this week → ready for INT
  • RSAC/SMO: @Rittwik
  • INT: James Li

Quick demo by Alex for the new NTSim function

00:2040SMO/Integration package/charts

ONAP Gerrit

O-RAN-SC Gerrit - MERGED

O-RAN-SC Gerrit - REVIEW


00:3055ONAP Use casesN.K. Shankaranarayanan 
  • Meeting related to SIM and honeycomb - Shankar did invite using the zoom from the ONAP SON meeting - but 12:00 UTC
  • reuse of ONAP SON meeting - 7am EST - 12:00 UTC 

--

Slicing Use case:WIPRO lead & team stepping back somewhat  ... (mail from Ahila:

Shankar created a JIRA 

Jira
serverONAP Jira
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyDCAEGEN2-2987
 
as a placeholder to converge on VES formats for SON use case.

00:56O1 Models for R1

Shankar submitted a contribution to O-RAN WG2 on the notion of primary and secondary yang models. Tomorrow is a holiday and so I have he requested that it be on the agenda on Dec 9 WG2 meeting. The WG2 chairs said ok.

00:57LFN-developer-testing-forumTimo Perala 

Encouraging submissions to LFN DTF event in 10-13 Jan 2022. Call open now - Dec 3rd (ish (smile)).


01:00End





00:xx

O-RAN SC: Copying/Releasing helm charts in O-RAN-SC nexus repo

https://jira.linuxfoundation.org/plugins/servlet/theme/portal/2/IT-22586 (maybe restricted access?!?!)

Status: canceled (Nexus does not support Helm chart distribution)

Question from O-RAN-SC to ONAP: What is possible in ONAP nexus?

Sébastien Determe: adds some info

Idea: store the artifacts - instead of helm - 

Jira
serverLinux Foundation Jira
serverId786ecce4-c7f8-3725-b80d-ceab920b9b14
keyRELENG-3837

Christophe Closset: ONAP on the way to move for helm charts to gitlab....



Action items

  •  



Info
iconfalse

17:00 UTC, 09:00 PST, 12:00 EST,  17:00 GMT, 18:00 CET, 19:00 EET, 22:30 IST, 01:00 CST (Thurs), 02:00 JST (Thurs)


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


Calendars:

Summer Daylight Savings time eventually stabilizes to:
9am PDT | 12pm EDT | 16:00 UTC | 17:00 BST | 18:00 CEST | 19:00 EEST | 21:30 IST | 00:00 CST (Thurs) | 01:00 JST (Thurs)

Winter (non-DST) time eventually stabilizes to:
9am PST | 12pm EST | 17:00 UTC | 17:00 GMT | 18:00 CET | 19:00 EET | 22:30 IST | 01:00 CST (Thurs) | 02:00 JST (Thurs)

(During Winter→Summer DST changeover follow US time. Summer→Winter DST changeover follow Europe time)


Table of Contents

Table of Contents

Attendees

Informed

Discussion items

TimeItemWhoNotes
00:00Admin

Next meetings: 

2021-12-01: Martin Skorupski 
2021-12-08: John Keeney 
2021-12-15: Martin Skorupski  
2021-12-22: proposal: canceled
2021-12-29: proposal: canceled
2022-01-05: proposal: canceled
2022-01-12: Martin Skorupski 

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

O-RAN-SC ToC


Projects:
  • Non-RT-RIC: John Keeney
    • working on rApp for the slicing use-case
    • open questions - e.g. slice id values 
    • focus on rApp "management" - life-cycle-management
  • SIM: Alex Stancu
    • working on the network-slicing use case
      • subscription to a VES stream
      • PM-Job management
      • Sending PM ves messages as "stndDefined"
      • CM for radio-resource-management per slice
      • CM du functions (Cell → slice)
  • OAM: Martin Skorupski
    • "validation" of the new NTSim functions as listed above
    • release note
  • O-DU:HariomGupta(HCL) / @Vidhu.  
    • cm (3GPP yang - rel17-draft)
    • pm in ves:measurement to O-RAN-SC-SMO
    • stabilize code this week → ready for INT
  • RSAC/SMO: @Rittwik
  • INT: James Li

Quick demo by Alex for the new NTSim function

00:40SMO/Integration package/charts

ONAP Gerrit

O-RAN-SC Gerrit - MERGED

O-RAN-SC Gerrit - REVIEW


00:55ONAP Use casesN.K. Shankaranarayanan 

Shankar created a JIRA 

Jira
serverONAP Jira
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyDCAEGEN2-2987
 
as a placeholder to converge on VES formats for SON use case.

00:56tsc/topic/86928483#8256)
  • Will be further discussed at Slicing Use Case team.
  • Use case remains important for O-RAN Slicing discussions.
  • SON Use case:
  • "Sleeping Cell - A1 Enforcement Simulator"
    • Possible to have as Use case for Jakarta ??? Running out of time for Jakarta.
    • Offline call & further discussions needed probably.
    • Pawel Slowikowski Already a PoC - Missing O1 parts - (RANSIM netconf)
      • Maybe RANSIM capabilities here? Please Join SON use case call ... or talk offline.
  • Want to make progress on A1 enhancements in ONAP Jakarta (Slicing / SON)

    • Will discuss on ONAP J usecases/requirements sub-committees next/coming weeks.

    ONAP RANSim vs OSC Simulators - Try bring together use cases across ONAP / OSC ?

    • ONAP RANSim based on Honeycomb, OSC O1 simulators based on Netopeer netconf servers  (All OSC O1 simulators based on same platform)
    • Different simulators have different focus - some on use-case logic vs interface/connectors.
    • Will hopefully be easier to mix & match deployments / use cases / simulators across OSC and ONAP should be easier as SMO deployments become more modular & composable.
    • Note also Sleeping Cell Simulator from Samsung in ONAP Integration (Marcin Krasowski, Pawel Slowikowski, Mateusz Zawadzki)
    00:30
    O1 Models for R1

    Shankar submitted a contribution to O-RAN WG2 on the notion of primary and secondary yang models. Tomorrow is a holiday and so I have he requested that it be on the agenda on Dec 9 WG2 meeting. The WG2 chairs said ok.

    00:57LFN-developer-testing-forumTimo Perala 

    Encouraging submissions to LFN DTF event in 10-13 Jan 2022. Call open now - Dec 3rd (ish (smile)).


    01:00
    • O1-CM Models over R1

      STL-AO-2021-11-15-WG2-C-ONAP-ORAN-Harmonization-O1-Input.pptx

      (Note, you may need to download and view offline if the content appears garbled)

      • For O1-CM enabling functions in R1, then R1 models should be based on O1 models - but probably need something more, extending main O1 model - "Primary Model & Secondary Models"
      • How is secondary model synced with primary model? E.g. In ONAP CPS the TBDMT function does this.
        • Expressiveness of mappings make make it possible/difficult to maintain such mappings ... or would richer logic be needed/possible? FFS.
      • Needs discussion in WG2 (R1 aspects) & WG10 (OAM/SMO aspects) - likely too late for November train at this stage (sad)
    00:56End





    00:xx

    O-RAN SC: Copying/Releasing helm charts in O-RAN-SC nexus repo

    https://jira.linuxfoundation.org/plugins/servlet/theme/portal/2/IT-22586 (maybe restricted access?!?!)

    Status: canceled (Nexus does not support Helm chart distribution)

    Question from O-RAN-SC to ONAP: What is possible in ONAP nexus?

    Sébastien Determe: adds some info

    Idea: store the artifacts - instead of helm - 

    Jira
    serverLinux Foundation Jira
    serverId786ecce4-c7f8-3725-b80d-ceab920b9b14
    keyRELENG-3837

    Christophe Closset: ONAP on the way to move for helm charts to gitlab....



    Action items

    •