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: 

2022-03-02: John Keeney
2022-03-09: John Keeney (Martin ooo)

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

2022-03-16: John Keeney
2022-03-23: Martin Skorupski 

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

2022-03-30 John Keeney



00:25LFN workshop

x-Community discussion

update 2022-02-17:

There are 2 different events:

March 14, 15:

April 12 - 14:

00:25ONAP Use cases

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

In the case of PM VES format, there are two templates/files in OSC which look a little different in the body/payload part of the msg.
Would like to discuss which one we should build upon.

1. OSC sim/o-du Slicing PM VES msg and template: There is a sample PM VES msg in the Slicing Use Case wiki: 

Is it generated from the code in this sim project o1-interface repo?
sim/o1-interface · Gerrit Code Review (
with this template file?

2. OSC oam VES template: There is a PM msg template and other template files in the oam repo
oam · Gerrit Code Review (
such as this PM msg template 

Please use item 1 (smile)

00:35SMO/Integration package/charts

jenkins and its proxy configuration issues to be addressed

deployment of the closed-loop use case

addressing OOM enhancements related to DMaaP 



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