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
- Andrew Lamb
- Chris Dent (VMWare)
- Christophe Closset (AT&T)
- David Allabaugh
- HariomGupta(HCL)
- Kamel Idir
- Kevin Tang
- Krystian Kedron
- Lathishbabu Ganesan
- Marcin Wilk (Samsung)
- Sandeep Shah
- N.K. Shankaranarayanan
- Scott Blandford
- Sonia Sangari
- Timo Perala
- May not have captured a full attendee list for this meeting ... please add/remove yourself
See also / co-located (ONAP/O-RAN-SC/SMO - Meeting)
- Co-located with ONAP 2021-08-18 Meeting notes (ONAP/O-RAN-SC/SMO - Meeting)
Contents
Recording
Notes:
Housekeeping:
OSC SMO Meeting Series: 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
Vacation plans in coming weeks:
- John Keeney will be unavailable for call on 11Aug ... Call will happen next week, but OSC NONRTRIC will likely not be covered. Recording will be made available
OSC Project roundup:
NONRTRIC (John Keeney)
No update this next week.
SIM (Alex Stancu)
No update
OAM (Martin Skorupski)
- No update
O-DU (HariomGupta(HCL))
- No update.
News from OSC TOC call this week
Releasing Helm Charts from OSC
- O-RAN SC: Copying/Releasing helm charts in O-RAN-SC nexus repo: Cannot be done in Nexus: See Support Ticket
- New LF JIRA Story to use Artifactory: RELENG-3837 - "[O-RAN] - Helm charts copy and release"
- Christophe: ONAP considering using GitLab for this, may affect how Helm Charts are distributed/released in ONAP
CM Notification & VES
- Ref discussion from last week: ONAP 2021-08-11 Meeting notes (ONAP/O-RAN-SC/SMO - Meeting)
- Shankar: Reference to zip file from 3GPP with defns & schemas etc for CM notifications: https://www.3gpp.org/ftp/Specs/archive/28_series/28.532/28532-g81.zip
- Marcin: Trying to validate the files, but additional files are referenced & need to be found.
- Marcin: Unclear how VES collector will be able to handle cross-references in yaml files.
- Should be enough details there to demonstrate MOICreation VES event creation & validation
- VES collector in OOF SON: Marcin & N.K. Shankaranarayanan & Sandeep Shah:
- Ref slide 16 in this June 2021 LFN slide deck for the ONAP-SON use case.
- Where is VES message processing done in SDNR?:
- In ccsdk/northbound. Using VES 7.1 currently
- (Need to update to VES 7.2 - ref https://jira.onap.org/browse/DCAEGEN2-2880) .
- See https://wiki.onap.org/display/DW/CM+Notification+Support+in+ONAP
- In ccsdk/northbound. Using VES 7.1 currently
- Marcin: Re https://jira.onap.org/browse/DCAEGEN2-2880 (support for VES 7.2)
- Seems VES 7.2 is already (partly?) supported in ONAP Honolulu DCAE VES Collector. Confirmed by Martin Skorupskifor FM at least, with simple schema.
- VES Collector: gerrit.onap.org:29418/dcaegen2/collectors/ves
PM Streaming in O1:
- Shankar: In ORAN O1 streaming must be ASN.1-based. Why just ASN.1? 3GPP doesn't seem to restrict to ASN.1 only.
- Martin Skorupski Will check in 3GPP spec and address question to WG10 team.
ONAP SMO deployment options
- Update from last Friday meeting:
- Minutes: https://wiki.onap.org/display/Meetings/2021-08-13+Meeting+notes
- Presentation from Samsung team about their prototype CNF-like simulator & usecase Krystian Kedron Pawel Slowikowski
- Updates etc of demo presented about 1 year ago here.
- Implementing A1 policy deployment using ONAP Control Loop concepts.
- Slides: https://wiki.onap.org/download/attachments/107252299/ONAP%20CNF%20based%20A1%20Policy%20Enforcement%20Simulator.pptx?version=1&modificationDate=1628865980000&api=v2
- Christophe: Working on deploying OSC O-RU & O-DU simulators deployable as helm-chart-based CNFs. (Similar to ONAP vFW deployment work)
- WIP: Configuring the simulators etc ...
- Deployment part of the PoC seems pretty stable now as per earlier meetings - pending availability of helm charts from ONAP & OSC.
- Ref topic Helm charts from OSC above
Q&A:
- ONAP SON Use case: N.K. Shankaranarayanan
- Mostly O1 based until now. (PCI & ANR until now PM & CM)
- Working on how to include A1
- Will be discussed further at ONAP Use case realization call next Monday.