2021-07-28 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
Jul 28, 2021
Attendees
Incomplete attendance list this week. Sorry, I didn't get a snapshot of attendees
@John Keeney (Ericsson EST)
@Martin Skorupski
@Alex Stancu
@Andrew Lamb
@Byung-Woo Jun
Chris Dent (VMWare)
@Former user (Deleted)
Fernando (Fred) Oliveira
Gervais-Martial Ngueko (AT&T)
@Hariom Gupta (Deactivated)
@Kamel Idir
@Krystian Kedron
@Lathishbabu Ganesan
@marcin krasowski
@Pawel Slowikowski
NK Shankaranarayanan (Sterlite)
Sebastien Determe (AT&T)
Stanislav Marszalek (Samsung)
@Vidhu (Deactivated)
@William DIEGO
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-07-28 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.
Vacation plans in coming weeks:
@John Keeney (Ericsson EST) will be unavailable for call on 11Aug ... Will discuss next week if this/other calls should be cancelled, depending on availability of key attendees.
OSC Project roundup:
NONRTRIC (@John Keeney (Ericsson EST))
Little new to report since last week as team members on vacation
A1 Policy Functions in ONAP - Istanbul M3 approaching
Work continues on A1 Adapter & A1 Policy Management Service extensions.
Continue Release E planning
Looking at how to deploy & LCM Apps in OSC E
Based on work in ONAP: https://wiki.onap.org/display/DW/TOSCA+Defined+Control+Loops%3A+Architecture+and+Design
While this is based on older work on ONAP Control Loops/Clamp - it is basically a full re-architect & build.
Still at a very early stage, not yet ready to present / demo ... Hope to demo/present at upcoming RSAC meetings a few weeks.
Current prototyping going very well - using the OSC D "Link Monitor" Apps as requirements drivers & "pipe cleaner".
SIM (@Alex Stancu)
@Martin Skorupski : Alex is working on an issue with ODL & Netopeer on RestConf-Netconf translation.
OAM (@Martin Skorupski)
Release planning & examining use case proposals
O-DU (@Hariom Gupta (Deactivated))
E-Release Planning
Discussing with O-DU-High&O-DU-low team for O1 config parameters - based on 3GPP parameters.
News from OSC TOC call this week
OSC D-Release PR has still not happened ... soon ..?
OSC E-Release Preparation: Input from RSAC
Some action likely needed to support new O-RAN license ... PTLs await further input from TOC & legal
https://lf-o-ran-sc.atlassian.net/wiki/display/TOC/#ORANSCTechnicalOversightCommittee(TOC)-20210728
OSC Release E usecases:
New version of E-Release RSAC slide deck https://lf-o-ran-sc.atlassian.net/wiki/download/attachments/12518627/E_rel_v2.pptx?api=v2
Proposals are still very early stage: more detailed discussion required - attend RSAC meetings for more details:
Usecase: Disaggregating VES: "Network Telemetry Improvement Proposal"
See slides #99+ in slides above
Discussed at RSAC/SMO call last week:
Unsure if this will affect spec/standardization for VES
Suggestion PoC in OSC (E release) then upstreamed to ONAP J+
Perhaps discussion is needed and would be welcome in ONAP at this stage - prior to PoCing in OSC?
Usecase: "Slice Resource Quota Provisioning and Assurance"
See slides #113+ in slides above
O1 Closed loop use case - for slice resource assurance.
Based on "3.12 Use case 12: NSSI Resource Allocation Optimization" in https://oranalliance.atlassian.net/wiki/download/attachments/170655795/O-RAN.WG1.Use-Cases-Detailed-Specification-v06.00.02.docx?api=v2
Just the O1 part, not the O2 part. (excludes sequence 3b in flow diagram)
For the E-Release, the rApps & SMO & OAM parts would be very similar to the OSC-D closed loop use case (O-DU/O-RU FH recovery)
... But alot of work will be needed to support the function & support required CM in O-DU
@John Keeney (Ericsson EST) rApp/NonRTRIC: Hopefully we can use this usecase to further demonstrate Control Loop rApps (will be based on similar activities for Control Loops in ONAP)
ONAP SMO deployment options
@Martial: No major update on the deployment work:
Need to wrap up initial PoC for ONAP Istanbul, but not tied by ONAP M3 date
@Martial Next step will look at CNF deployment
CNF Deployment / Combined PoCs:
@Pawel Slowikowski Good overlap with Samsung Demo for last year - deploying a simulator CNF
@John Keeney (Ericsson EST) Can we also combine with ongoing PoC work on rApps / Control Loops in ONAP?
Lets discuss if we can pull 3 PoC workstreams together
Q&A:
PM Collection / VES PMMapper
@33:30 in recording
@Pawel Slowikowski @Krystian Kedron @Stanislav
Struggling with PM Mapper for O1 PM-Bulk measurements - can only use bulk collection (ves:fileReady & File collection), but PMMapper translate to VES events does not seem to work very well ...
Potential to improve how PMMapper → VES event translation
@Stanislav presented slides:
Difficulty identifying temporal granularity of the individual events
Semantic of the Granularity period is misleading? wrong?
@Martin Skorupski Is the start/end times in header? This would define the granularity?
Granularity should be inside the message? - Would have a knock on effect in spec/standardization.
Likely that new approach to use stndDefined schemas for 3gpp events might work around this?
@Martin Skorupski will reach out to some interested parties.
Issues mapping meastype with measvalue
Version, VESVersion, Priority, Domain seems to be hardcoded in VES PMMapper. SourceID is missing.
may be a broader with VES Collector in general
@Martin Skorupski Should start by creating tickets in JIRA - VES Collector & PMMapper
DCAEGEN2-2874 PM Mapper output - sMeasTypesList
DCAEGEN2-2873 PM Mapper output - granularityPeriod issue
SON Usecase:
@57:10 in recording
@Shankar: SON Use case uses VES PM messages direct to VES Collector (bypassing PMMapper)
To be O1 compliant should use File-based PM ... Ref WG10 in O-RAN
@Shankar: Now working with Sterlite - but continues to be committed to SON use case
@John Keeney (Ericsson EST) A1 Policy for SON use case discussed at ONAP Use Case Realization Call this week