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
- John Keeney
- Martin Skorupski
- Alex Stancu
- Andrew Lamb
- bhanu chandra
- Christophe Closset (AT&T)
- user-4594e
- Fernando (Fred) Oliviera
- Gervais-Martial Ngueko (AT&T)
- HariomGupta(HCL)
- Kamel Idir
- Marcin Krasowski
- Marcin Wilk (Samsung)
- Nicholas Karimi
- N K Shankar
- Scott Blandford
- Sonia Sangari
- Timo Perala
- Vidhu Shekhar Pandey
- William DIEGO
- Zu Qiang (Ericsson)
- 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-23 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
- O-RAN has declared that recording are kept for 2 weeks only. Does this apply to us?
- Is this a requirement, a privacy issue or a cost issue?
- Not sure - the recording storage quota that we use is currently full - so we may need to delete old cloud recording?
- All past recording are also available as files uploaded to the wiki pages - May be a storage issue later, but no plans to delete as yet.
OSC Project roundup:
NONRTRIC (John Keeney)
- Ready for OSC D release. Just wrapping up last of the deployment charts etc, with latest version number, branching etc.
- Hope to double check ONAP Policy version of O-RU-FH recovery usecase is working as expected
- Thanks to Martin Skorupski Alex Stancu Alex Dehn & entire team for help with Lab setup. All workign fine now.
- John Keeney Martin Skorupski Alex Stancu - Will have a quick chat about double-checking integration environment. Looks good!
- John Keeney Brief feedback of what happened at OSC TOC call this week: https://wiki.o-ran-sc.org/display/TOC#ORANSCTechnicalOversightCommittee(TOC)-20210623 (Minutes not yet updated at time of writing)
- OSC D Release will likely be delayed for a few days.
SIM (Alex Stancu)
- Ready for release.
OAM (Martin Skorupski)
- Ready for release
OSC Release D Integration:
- Kamel Idir verifies that Docker Compose for OSC D release integration environment is working fine - OAM, NONRTRIC, SIM (O-RU, O-DU). https://gerrit.o-ran-sc.org/r/gitweb?p=oam.git;a=tree;f=solution/integration
- Running with VM 16GB, 4CPU ... but needs 32GB.
- Any chance of a K8S deployment?
- Now have access to add Helm Chart updates for D Release
- NONRTRIC charts are almost fully complete.
- OAM release C versions need to be updated, but basis will be same.
O-DU (HariomGupta(HCL))
- Local testing integration with O-DU-Low seems OK, but struggling with IPv6 in OSC Lab.
- Messages being rejected when IPv4 is used instead.
- Will share logs etc with Martin Skorupski to diagnose.
- Issue is most likely with Lab setup rather than functions.
- John Keeney Is OTF integration going ahead?
- HariomGupta(HCL) No update.
- Unsure who is driving OTF in OSC currently.
ONAP Requirements Subcommittee
- Re Email from Alla: https://lists.onap.org/g/onap-requirements-sub/message/1985 Timo Perala @NK Shankar
- Next Req subcommittee meeting will focus on ONAP-O-RAN Integration https://lists.onap.org/g/onap-meetings/ics/invite.ics?repeatid=32519
- Next meeting July 5th (limited participation from USA?)
- Unsure what will be discussed. John Keeney Will check with Alla
- Followup: Likely to be postponed. See also https://lists.onap.org/g/onap-requirements-sub/message/1986
ONAP SMO deployment options (Christophe Closset (AT&T) & Amar Kapadia (AARNA))
- REF: 2 Weeks ago: Proposal for an ONAP deployment specific for an ORAN SMO
- @Christophe : Meeting upcoming
- https://lists.onap.org/g/onap-meetings/viewevent?repeatid=37969&eventid=1192141&calstart=2021-06-25 bhanu chandra
- https://wiki.onap.org/pages/viewpage.action?pageId=103422272
- (Updated afterward: Minutes & Recording: https://wiki.onap.org/display/Meetings/2021-06-25+Meeting+notes)
- Attempting to replicate functionality in OSC OAM/NONRTRIC/SIM demo - based on OSC charts.
- Mainly updating charts etc.
- Certs need updating
- Will be testing in ONAP WindRiver lab - setup etc. Might be a good place to collaborate.
- John Keeney Any update on how to reuse OSC & other external components?
- @Christophe, will be challenging in OOM, & need to reuse structure & some charts from OOM
- John Keeney Any ideas where SMO would be different from "Full ONAP"
- @Christophe: Plan to start with OSC charts/flavour ... then depends on Usecases ...
- Hope to be able to make use of the override files to create different flavours .. aiming for something similar to OSC version
- John Keeney Probably need different versions for different usecases
- @Christophe ... OOM have this same idea to have multiple flavours. Discussion gets broader when non-ONAP components are added.
- @NK Shankar ... Should also consider SON and Slicing usecases.
- John Keeney Recall that the OSC D release usecase is not real world ... and will mature in coming releases. Currently mostly treated as an integration requirements driver
- @Christophe @ @NK Shankar Need to consider diversity of DCAE components used. Also need to figure out how different simulators could co-exist.
- Lets continue discussions on Friday Call?