Informed
Please add/remove yourself. Thanks!
Time | Item | Who | Notes |
---|---|---|---|
00:00 | Admin | Next meetings: 2022-02-23: Martin Skorupski | |
00:05 | O-RAN-SC | O-RAN-SC PTLs | O-RAN-SC ToC
|
00:30 | ONAP | David McBride | log4j issues addressed in ONAP → Maintenance Istanbul Release
Jakarta Release - M3 in early March - release in June |
00:35 | LFN workshop | Timo Perala | x-Community discussion
update 2022-02-17: There are 2 different events: March 14, 15: April 12 - 14: |
00:00 | ONAP Use cases | We have a JIRA for the SON Use Case 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 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. 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? 2. OSC oam VES template: There is a PM msg template and other template files in the oam repo Please use item 1 | |
00:50 | SMO/Integration package/charts | Update
| |
01:00 | End | ||
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 - Christophe Closset: ONAP on the way to move for helm charts to gitlab.... |