Skip to end of metadata
Go to start of metadata

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)

Meeting ID: 890 6970 8424


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



Discussion items


Next meetings: 

Please follow the calendar

US/Canada: Daylight Savings Starts 13 March.  Eastern Daylight Time is UTC-4 

2022-03-16: John Keeney   (Follow US Local time - 1 hour earlier for Europeans & countries without DST)
2022-03-23: Martin Skorupski  (Follow US Local time - remains 1 hour earlier for Europeans & countries without DST) 

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 @ 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: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
DCAEGEN2-2987 - Getting issue details... STATUS

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

DCAEGEN2-2986 - Getting issue details... STATUS

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

00:25A1 in SON use case & Slicing

Should be planned for ONAP "K" → REQ → ....

3GPP copyright issue
  • Struggling with 3GPP copyright / reuse.
00:27SMO/Integration package/charts

update send by Chris and Seb

00:30Hello from DTEvgenii Limonov 

DT - working on ONAP 

working on Non-RT RIC and how to realise it with R1 interface and how to onboard apps

Observation initially

Very Welcome (big grin)

LFN workshop

There are 2 different events:

March 14, 15: (mini event) - x-Community discussion

Topics are:

April 12 - 14: (ones)



O-RAN SC: Copying/Releasing helm charts in O-RAN-SC nexus repo (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 -  RELENG-3837 - Getting issue details... STATUS

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

Action items