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

Jun 9, 2021

@John Keeney (Ericsson EST)
@Martin Skorupski
@Alex Stancu
@Amar Kapadia
@Andrew Lamb
@Bhanu Chandra K
Christophe Closset (AT&T)
@Former user (Deleted)
Gervais-Martial Ngueko (AT&T)
@Hariom Gupta (Deactivated)
@Kamel Idir
@Lathishbabu Ganesan
N K Shankar
@Pawel Slowikowski
@Scott Blandford
Sebastien Determe (AT&T)
@Sonia Sangari
@Timo Perala (Nokia)
@Vidhu (Deactivated)
@William DIEGO
Sorry - didn't manage to get a full attendees list for this meeting ... please add/remove yourself

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.
- 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.

Working hard on integration & documentation tasks now for OSC D release
- Should soon have access to the it/dep
@John Keeney (Ericsson EST) @Martin Skorupski @Alex Stancu, Felix & Mahesh - Hope we can catch up to figure out our way through the e2e integration tasks for OSC D release
@John Keeney (Ericsson EST) Brief feedback of what happened at OSC TOC call this week: https://lf-o-ran-sc.atlassian.net/wiki/display/TOC/#ORANSCTechnicalOversightCommittee(TOC)-20210609 (Minutes not yet updated at time of writing)

Working on deployment & integration
Considering a DNS - especially for IPv6 address (E release maybe, if needed)
Working on docker-compose for integrated deployment of SMO/OAM/SIM/NONRTRIC functions
- Topology Service:
  - Collaborative work with ONAP Modelling/O-RAN Alliance modelling

Proposal for an ONAP deployment specific for an ORAN SMO
- Provide tuned override files in OOM for a standalone ONAP SMO
  - Can provide multiple flavours .. e.g. small/medium etc
- Current OOM override files are quite out of date & may not be robust.
@John Keeney (Ericsson EST) Any chance of deploying non-ONAP functions? e.g. NONRTRIC functions in OSC
- Christophe: Plan to start small with OOM initially (so no ?)
  - Could perhaps deploy non-ONAP functions (e.g. NONRTRIC, simulators etc) as CNFs ?
  - Not sure CNF is appropriate for SMO/NONRTRIC platform functions - Possibly a good idea for simulators etc that are CNFs/xNFs in the RAN
  - O2 (WG) is partly relevant for CNFs (and maybe for apps) - but not for SMO internals
Please discuss more before officially proposing this PoC in ONAP
Ref: https://jira.onap.org/browse/REQ-887