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: 

Please follow the calendar

Europe: European Summer Time Starts 27 March CEST is UTC+2

  • 2022-03-30 John Keeney (Usual local time in US & Europe, remains 1 hour earlier for countries without DST) 

Continues until October  @ 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)

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

O-RAN-SC ToC

00:10SMO Package

update send by Chris and Seb

  • CI/CD pipeline in Jenkins working; deployed in POWDER lab
  • Reports from tests now appear during review process

Documentation

00:103GPP copyright issue
  • Struggling with 3GPP copyright / reuse.
00:11A1 in SON use case & Slicing

Should be planned for ONAP "K" → REQ

  • first init steps please follow up the related SON use case meeting
  • abstraction of xApp in RAN SIM - focus on A1 interfacing
00:20VES syntax/schema

VES stndDefined

END






00:21ONAP Use cases
  • Ransim: Evolving (slowly) towards Netopeer from Honeycomb Vishal Varvate  
    • Comments welcome from Alex Stancu Martin Skorupski 
    • A1 in SON use case & RANSim (K Release +)
      • (Also being discussed in Slicing use case K Release +)
      • Next release in ONAP K. - Will start with update in ONAP REQ.


We have a JIRA for the SON Use Case

Jira
serverONAP Jira
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyDCAEGEN2-2987

The task to converge on the best VES format for FM/PM/CM messages for the SON use case (and other use cases?) going forward

Jira
serverONAP Jira
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyDCAEGEN2-2986

Open issue in VES-CM-Update notification and its mapping to the NETCONF/CM tree.





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

  •