2021-09-15 Meeting notes - Joint OAM / NONRTRIC / SIM SCRUM meeting
Time & Location:
Meeting Detail: Times & Joining Info
Wednesdays at 16:00 UTC in Summer (DST), 17:00 UTC in Winter !
Zoom Bridge : https://us02web.zoom.us/j/89069708424?pwd=aGJOZm54eTUxd0FXR0VCU1N0ejBrUT09
Ensure you are signed into your Zoom account to join.
Meeting ID: 890 6970 8424.
See the Calendar: (https://lists.o-ran-sc.org/g/main/calendar)
NOTE: During the "Daylight Savings Time" changeover periods (US vs Europe vs Asia) the time of the meetings may fluctuate.
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
Date
Sep 15, 2021
Attendees
@John Keeney (Ericsson EST)
@Martin Skorupski
@Alex Stancu
@Andrew Mayer
@Chris Dent
@David Allabaugh
@Dibas Das
Fernando (Fred) Oliveira
@Hariom Gupta
@John Paul Lane
@Jakub Dominik
@Kamel Idir
@Kevin Tang
@Krystian Kedron
@Lathishbabu Ganesan
@N.K. Shankaranarayanan
@Pawel Slowikowski
Rafal Wrzesniak (Samsung)
@Sonia Sangari
@Stanislav Marszalek
Christophe Closset (AT&T)
@Timo Perala (Nokia)
@Vidhu (Deactivated)
@William DIEGO
@Zu Qiang
May not have captured a full attendee list for this meeting ... please add/remove yourself
See also / co-located (ONAP/O-RAN-SC/SMO - Meeting)
Co-located with ONAP 2021-09-15 Meeting notes (ONAP/O-RAN-SC/SMO - Meeting)
Contents
Recording
Notes:
Housekeeping:
OSC SMO Meeting Series: Reminder from previous weeks:
OSC SMO calls now move to its own time slot - Thursdays
See OSC RSAC Calendar: https://lf-o-ran-sc.atlassian.net/wiki/display/RSAC/calendars
(Note this meeting to open to anyone, including non-ORAN members)
We will maintain this slot for ONAP Alignment, and try flag issues/question to/from SMO meetings.
OSC Project roundup:
NONRTRIC (@John Keeney (Ericsson EST))
Hoping to present some slides to RSAC tomorrow (rApps in E-Release) - postponed from last week
https://lf-o-ran-sc.atlassian.net/wiki/display/RSAC/RSAC+Meetings https://lf-o-ran-sc.atlassian.net/wiki/display/RSAC/calendars
Will focus on rApp platforms & R1 Service exposure/gateway/delivery
Wrapping up M4 issues for A1 Policy functions in ONAP
Experimenting with making DMaaP messages available to rApps over the Service Exposure function via the Information Coordination service
e.g. VES information from the RAN
Possible precursor for R1 data coordination functions until they crystalize in the specs
Will follow up with LF about making Helm charts available in a chart repo ...
Struggling with a issue with Jenkins verify tasks in OSC (Docker verify task fails ... working through candidate solutions with LF ... possible environment issue)
SIM (@Alex Stancu)
Working on call home via TLS in O1 (ofh-mplane) simulator.
OAM (@Martin Skorupski)
Working with O-DU team for yang model (Cell configuration)
Working toward Slicing assurance closed loop usecase
to include TMF apis slice management functions
What if Yang models are different? (e.g. O1 vs OFH-Mplane vs simualtor) Which function should handle/isolate this?
Contacted via @N.K. Shankaranarayanan about end-to-end slicing in ONAP for OSC/ONAP alignment
currently working at O1/A1 type messages, so haven't gotten down as far as OFH yet.
Will bring up at slicing use case call
Also ORAN-slicing ↔ ONAP-slicing discussions seem to have stalled ... need to be restarted.
O-DU (@Hariom Gupta (Deactivated))
@Vidhu (Deactivated) focusing on Yang modules for cell configuration, e.g. which parameters etc.
Some parameters already in the hello-world model - reuse, augment or replace?
Working with @Martin Skorupski
Slicing assurance use case parameter .. .working with @Former user (Deleted)
Still figuring which parameters are appropriate.
Discussing if PM should be file based on ves-based ... (see below)
News from OSC TOC call this week
No update
VES for PM
Lack of clarity when to use file-based vs event-based vs stream-based for O1 PM
Depends on use case / metric ... probably need multiple for any function
Ongoing discussions in SMO/RSAC call tomorrow
Proposal for VES PM event would not be O1 spec compliant right now
Discussion should happen in WG10, and likely in 3GPP
CM Notifications - Updates to SDNR
(Recording @ 00:35:00 - 01:03:06)
Marcin Wilk, Rafal Wrzesniak (Samsung)
Slides & sample CM-Notification VES event.
StdDefined VES event - using provMnS.yaml - NotifyMoiChange
Some issues with the NotifyMoiChange path parameter
... how to set it ... how to map to yang path? (Does it define yang path?)
Currently message is not used in SDNR ... todo
ref 3GPP TS 28.532 SA5 Rel16 - link https://www.3gpp.org/ftp/Specs/archive/28_series/28.532/28532-g81.zip
Added necessary schema (from zip above) to VES Collector as external schema (& updated schema config file with topic etc)
DMaaP Topic: unauthenticated.SEC_3GPP_PROVISIONING_OUTPUT
Code in repo (WIP) - Link in Gerrit:
@Martin Skorupski @N.K. Shankaranarayanan @Alex Stancu - will work on how to create the CM notify message in simulators etc.
Related work using CM notify messages happening for updates to ONAP CPS:
Can be reused after parsed by SDNR as above
https://wiki.onap.org/display/DW/SDN-R+Feature+for+adding+cm-handle
Not handling CM-Notify in the case above ... but CM-Notify will be looked at too.
@N.K. Shankaranarayanan will bring relevant people together to join up?
@Pawel Slowikowski Where does CPS get message? From SDNR, or from DMaaP? Is message reparsed?
@Martin Skorupski Device → VES → Collector → DMaaP → SDNR (or elsewhere) → CPS ???
SDNR (or elsewhere) will add identifiers (CMHandle ??) of where the message came from for CPS