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
Attendees
- Incomplete attendance list this week. Sorry, I didn't get a snapshot of attendees
- John Keeney
- Martin Skorupski
- Alex Stancu
- bhanu chandra
- user-4594e
- Gervais-Martial Ngueko (AT&T)
- Kamel Idir
- Lathishbabu Ganesan
- Sonia Sangari
- Timo Perala
- William DIEGO
- 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-06-30 Meeting notes (ONAP/O-RAN-SC/SMO - Meeting)
Contents:
Recording
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)
- OSC D Release ready. Branch & staging done.
- Hoping to have a proposal on rApps & R1 in comining weeks.
SIM (Alex Stancu)
- Ready for release. Branch done.
OAM (Martin Skorupski)
- Ready for release Branch done.
- user-4594e 's work on Adapter is added to D Release branch
OSC Release D Integration:
- D Release delayed for another week. Vote at next week's TOC call
- Alex Stancu OSC lab now supports IPv6 - but will not enable until after the D Release.
- O-DU SIM now working with IPv4
O-DU (HariomGupta(HCL))
- Testing D-Release currently - all working (IPv4)
ONAP Requirements Subcommittee
- Last Week: Re Email from Alla: https://lists.onap.org/g/onap-requirements-sub/message/1985 Timo Perala @NK Shankar
- Will follow up next week
ONAP SMO deployment options (Christophe Closset (AT&T) & Amar Kapadia (AARNA))
- Ref: to last 2 meetings.
- Ref: Friday meeting Minutes & Recording from last week : https://wiki.onap.org/display/Meetings/2021-06-25+Meeting+notes)
INFO provided by from Christophe - 2021-06-30: (Presented by Martial)
Just a few notes:
- We have agreed with ONAP and other members of O-RAN SC to keep an ad-hoc call on Friday to discuss technical details for now (will remove this meeting once all details are sorted out and use the joint meeting to report status)
- Main comment from John is that we cannot consider an SMO deployment without having a way to deploy Non-RT-RIC as well as ONAP components (hence a debate on how this should materialize : extend OOM? )
- We have progressed on the POC in the meanwhile, Sebastien had an idea and has pushed a small repository on github to show what we are doing for now to create a unique installation for O-RAN, trying to implement the following idea:
- Started from IT/DEP repo, containing some Helm charts for ORAN (including Non-RT-RIC)
- Seems an embryo of using ONAP charts to deploy SMO components but sounded like a fork of ONAP charts
- Instead of copy pasting OOM charts, he create a git submodule referring to oom ONAP charts repo (to keep ONAP untouched)
- Rework the ORAN charts to map them to the OOM structure (like OOM'ized O-RAN charts)
- Try and build (created some makefiles, inspired from ONAP) then push them to a single chart repository
- Merged ONAP override and ORAN override to have a single file
- Created an Install script to deploy the charts in a single Namespace
- … it worked more or less
We plan to show that maybe on Friday call
- Initial (private) Github repo to have info from both ONAP & OSC - testing this approach.
- Copies & modifies scripts from OOM and OSC for now. (Git submodule)
- Will share link at Friday meeting
- Will probably move to ONAP OOM eventually
- No focus yet on CNFs etc yet.
- Relationship with ONAP CNFs & O2 is not clear yet.
After the Call: ONAP Release progress (David McBride )
- ONAP Intanbul M2 passed in ONAP TSC.