2021-09-01 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 1, 2021
Attendees
@John Keeney (Ericsson EST)
@Martin Skorupski
@Alex Stancu
Chris Dent (VMWare)
@damian.nowak
@David Allabaugh
@Kamel Idir
@kevin.tang
@Lathishbabu Ganesan
@marcin krasowski
Marcin Wilk (Samsung)
@Pawel Slowikowski
Sebastien Determe (AT&T)
@Sonia Sangari
@Timo Perala
@Vidhu (Deactivated)
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-01 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))
Preparing RSAC outline proposal for E Release - will hopefully present at next RSAC call (Thurs 9 Sept?)
Wrapping up some loose threads on A1 Policy Management in ONAP (M3 & M4)
SIM (@Alex Stancu)
Skipped - Alex on vacation
OAM (@Martin Skorupski)
Working with O-DU team for architecture & O1 aspects of RAN Slicing use case
O-DU (@Hariom Gupta (Deactivated))
Skipped
News from OSC TOC call this week
D-Release Maintenance Branching strategy
Query from @Former user (Deleted) about branching strategy for D Maintenance Release
@John Keeney (Ericsson EST) to reply directly. We use D ('dawn') git branch for D maintenance release changes, with a git Tag for the original release and another later git Tag for the maintenance release. Master git branch continues in parallel with changes synched from master branch to dawn branch using git cherrypicking.
Examples: https://trunkbaseddevelopment.com/branch-for-release/
Options: CherryPick from master or CherryPick to master - Whichever you prefer. (I prefer CherryPick from master)
... But branching strategies are like opinions (everyone has their own) .... See https://martinfowler.com/articles/branching-patterns.htm
@Martin Skorupski That's what OAM project does too.
PM over VES @damian.nowak
PM over VES (send PM events directly, rather than in files) is already supported since ONAP Casablanca (perf3gpp) - but performance/capacity will be very poor as n/w scales unless massive resources committed.
Comparison of text-based vs binary payload was compared before too. (JSON vs GPB - expect similar for ASN.1?)
From https://wiki.onap.org/display/DW/Casablanca+Release+Developers+Forum+Session+Proposals (ONAP Casablanca Dev Forum: JSON versus GPB)
May be suitable for very small deployments or demos/prototypes, but not large-scale production. (Expect 10k-100k nodes)
Would be challenging if there was a proposal to standardize this, or mandate support in actual "O-RAN nodes" - would increase cost as options are added.
(Additional challenges aligning with 3GPP etc)
Thanks Damian!
Update for ONAP Requirements Sub Committee (last week) @Timo Perala
@Timo Perala, Alla Goldner : ONAP Requirements subcommittee last week - request an update on areas where ONAP and O-RAN share interest.
Went well - lots of information
As expected, not enough time
Any deep dive on any of the topics mentioned would need alot more time & dedicated team for discussion
@Timo Perala will add slides
Hopefully can make a similar (but shorter & more focused) presentation to TSC at some stage soon.
Thanks to all for content & prep.
Not sure how to follow up ....
Disaggregated VES Discussion
Discussions continue at RSAC call Thursday 9th Sept
Important to have all relevant parties discussing before decisions are made, or risk unnecessary divergent implementations