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

Jul 7, 2021

Incomplete attendance list this week. Sorry, I didn't get a snapshot of attendees
@John Keeney (Ericsson EST)
@Martin Skorupski
@Alex Stancu
@Andrea Buldorini [TIM]
@Andrew Lamb
@Bhanu Chandra K
Christophe Closset (AT&T)
Fernando (Fred) Oliveira
@John Paul Lane
@Kamel Idir
@Lathishbabu Ganesan
@marcin krasowski
@Pawel Slowikowski
@Sonia Sangari
@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

OSC D Release done - Just need a final check in documentation etc for branch links, version numbers, tags etc..
Hoping to have a proposal on rApps & R1 in coming weeks.

Confusion exists with differences between nexus repos in OSC vs ONAP.
- OSC: https://lf-o-ran-sc.atlassian.net/wiki/display/ORAN/O-RAN+Developer%27s+Guide+to+CI+Resources+and+Processes+at+the+LF (Search for "nexus")
- ONAP: https://wiki.onap.org/display/DW/Required+Tools#RequiredTools-Server-BasedToolsandRepositories
- All urls/port numbers need to be changed & re-tested after release - snapshot versions disappear after 30 days.
- ONAP has a nice solution by using port 10001 for both staging & release.
Suggestion to ask LF to create a common repo/proxy that provides artifacts across LF projects
- Need to contact Trishan de Lanerolle to ask advice re OSC
- @Chistophe / @Alex Stancu / @Martin Skorupskiwill follow up in ONAP.
@Christophe: Suggest always using Release versions in helm charts - then use overrides etc to test staging/snapshot versions

Ref: to last 3 meetings.
Ref: Friday meeting Minutes & Recording from last week : https://wiki.onap.org/display/Meetings/2021-07-02+Meeting+notes)
@Christophe:
- Request to OOM/ONAP to provide a repo for built helm charts in nexus ... ongoing.
- Demo from last weeks shows a protoype of this in github - drawing charts from both ONAP & OSC (via git submodule) - built & stored in local repo.
  - Local repo & git submodule & build can be removed if ONAP and OSC makes charts available publicly.
  - A simple overarching chart / override can then use/fetch charts from both OSC & ONAP - to try out some use cases.
  - Ping @Christophe or @Gervais-Martial Ngueko (AT&T) to get access.
(@John Keeney (Ericsson EST) Also asked about getting a helm chart repo for OSC. https://lists.o-ran-sc.org/g/discuss/message/331)

(Timestamp 22:40 in recording)
@Byung gave a brief summary of ongoing work / proposal in ONAP for ASDs for CNF orchestration in ONAP. Input from @Fred also.
- https://wiki.onap.org/display/DW/O-RAN%3A+ASD+solution
- https://wiki.onap.org/display/DW/Application+Service+Descriptor+%28ASD%29+and+packaging+Proposals+for+CNF
- https://wiki.onap.org/display/DW/CNF+Orchestration+Functional+Architecture
- Goal for a simplified version of SOL001 CNF descriptor & deployment / onboarding - Currently very complicated & duplicated info in helm chart.
- O2 (SMO-O-Cloud) is still not settled. Currently working with SOL004 CSAR package to SDC then into repository for Orchestrator to use.
@Fred This is still all at proposal stage. An alternative SOL001 proposal is also under consideration / ongoing.
Work / Discussions still at a very early stage ... deliverables for Istanbul sill in flux. Will also update again when O2 gets clearer.
@Pawel Slowikowski Any plan to fully support ASD format in SDC etc ... e.g. in Portal etc
- @Byung Yes. Alot of work to do.
  - Push to get the work on ASD grounded first (Istanbul).
- Re SDC/UI - Yes, but it will likely take some time to get this through SDC etc. Hopefully can reuse alot of the NSD work is reusable. But all still very early.
Aiming for alignment with O-RAN.
- @Fred Note again, alternative proposal from Verizon will be discussed in WG10 next week.

Re Email from Alla: https://lists.onap.org/g/onap-requirements-sub/message/1985 @Timo Perala (Nokia) @NK Shankar
- Will follow up next week