Time & Location:
Meeting Detail: Times & Joining Info
Wednesdays at 16:00 UTC in Summer (DST), 17:00 UTC in Winter !
NOTE: During the "Daylight Savings Time" changeover periods (US vs Europe vs Asia) the time of the meetings may fluctuate. See the Calendar: (https://lists.o-ran-sc.org/g/main/calendar)
- 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 we follow US time. Summer→Winter we follow Europe time)
Zoom Bridge : https://us02web.zoom.us/j/89069708424?pwd=aGJOZm54eTUxd0FXR0VCU1N0ejBrUT09
Joining the meeting:
- Meeting ID: 890 6970 8424
- Dial in: (Local numbers)
+1 646 558 8656 US (New York)
+49 30 5679 5800 Germany
+49 69 3807 9883 Germany
+353 1 240 8941 Ireland
+46 8 4468 2488 Sweden
+46 8 5016 3827 Sweden
+358 3 4109 2129 Finland
+358 9 7252 2471 Finland
Date
Attendees
- John Keeney
- Martin Skorupski
- Alex Stancu
- Andy Mayer
- David McBride
- Dibas Das
- emmanuel sarris
- HariomGupta(HCL)
- Kamel Idir
- Konrad Bańka
- Krystian Kedron
- Lasse Kaihlavirta
- Lathishbabu Ganesan
- Marcin Krasowski
- N K Shankar
- Pawel Slowikowski
- Scott Blandford
- Sonia Sangari
- Timo Perala
- Sorry - didn't manage to get a full attendees list for this meeting ... please add/remove yourself
See also / co-located (ONAP/O-RAN-SC/SMO - Meeting)
- Co-located with ONAP 2021-05-05 Meeting notes (ONAP/O-RAN-SC/SMO - Meeting)
Contents:
Recording
- Recording (cloud)
Recording (MP4 - low res)
Notes:
Housekeeping:
- Reminder from previous weeks:
- OSC SMO calls now move to its own time slot - Thursdays
- See OSC RSAC Calendar: https://wiki.o-ran-sc.org/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.
- See OSC SMO Project meeting notes
OSC Project roundup:
NONRTRIC (John Keeney)
- Continuing work as reported in past weeks:
- Helm chart onboarding function
- Service exposure function
- O-RU/O-DU helloworld FH recovery use case scripts
- Control Panel extensions
- On track for OSC D release delivery
- We are testing a first version of a script for the O-RU recovery use case - currently based on test stubs for VES Collector and SDNC.
- Alex Stancu Martin Skorupski Lets take a quick call to check if it's correct?
- May be able to demo something in coming weeks
- Need to improve with our Sprint demos!
SIM (Alex Stancu)
- No major update
- Still working on CII badging
OAM (Martin Skorupski)
- No major update
- Cleaning up Jira ticker
- CII badging
- Working on nf-oam-adapter: https://gerrit.o-ran-sc.org/r/admin/repos/oam/nf-oam-adopter
ONAP Istanbul release planning
- David McBride (ONAP Release Manager) provided a good summary of Istanbul release date extension proposal - tbc by ONAP TSC
- https://wiki.onap.org/display/DW/Release+Planning%3A+Istanbul
- https://wiki.onap.org/display/DW/Long+Term+Roadmap
- ONAP I M1 is moved back to 20 May (approx), M4 16 Sept (approx) , Release 28 Oct (approx)
- ONAP J M0 & M1 (not yet set) - but requirements planning should open Sept-Oct 2021
- Gives us a rough idea of the window to feed in requirements from OSC.
- Still looking at 2 major releases per year, with maintenance releases in between.
- John Keeney We probably now need to pull back some of our ONAP J release plans into ONAP I.
O-RAN F2F - 01-14 June 2021:
- Will we hold our weekly meetings for those weeks? We welcome comments/suggestions.
ONAP Q/A (N K Shankar)
- Discussions still ongoing about what O1 Yang model would be exposed Northbound from CPS/NCMP - likely same as the actual O1 model, but there may be issues.
- Andy Mayer Essential to have consistent models. Configuration model may also be informed by topology model once it matures.
- Important that models remain faithful to O-RAN models.
- Slicing might be a good first use for the topology model, and check abstractions make sense.