DRAFT Copied from last week as a template.
Time & Location:
| Info | |||||
|---|---|---|---|---|---|
| |||||
Wednesdays at 16:00 UTC in Summer (DST), 17:00 UTC in Winter ! Zoom Bridge : https://us02web.zoom.us/j/89069708424?pwd=aGJOZm54eTUxd0FXR0VCU1N0ejBrUT09
|
Date
18
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)
- user-4594e
- Dibas Das
- David Allabaugh
- Fernando (Fred) Oliveira
- Gervais Martial NguekoDavid Allabaugh
- HariomGupta(HCL)
- Kamel Idir
- Kevin Tang
- Krystian Kedron
- Lathishbabu Ganesan
- Marcin Wilk (Samsung)Manoj Nair
- Sandeep Shah
- Sebastien Determe (AT&T)
- N.K. ShankaranarayananScott Blandford
- Sonia Sangari
- Timo Perala
- Vidhu Shekhar Pandey
- May not have captured a full attendee list for this meeting ... please add/remove yourself
...
- 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
...
- 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.Skipped
SIM (Alex Stancu)
- No updateSkipped
OAM (Martin Skorupski)
- No updateSkipped
O-DU (HariomGupta(HCL))
- No update.Skipped
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
PM over VES N.K. Shankaranarayanan
- (01:50-48:00 in recording)
- N.K. Shankaranarayanan : Slides to follow hopefully
- PM Data from RAN to SMO over O1 - using VES
- O1 is currently focused on file-based PM, with VES used for notifications to coordinate File collection.
- VES already used for FM and CM notifications etc
- Some sample / pre-spec / prototypes using VES messages to relay PM-like data to SMO
- O1 PM streaming: Specifies ASN.1 data over websocket (aligns with 3GPP)
- Suggestion/Proposal that JSON VES for PM Streaming might be useful too
- Suggest proposal to O-RAN WG10 & 3GPP - wider audience
- VES domain (3gpp 28.532 Annex B) - perf3gpp vs stndDefined
- perf3gpp is older (pre-stndDefined) - used in ONAP until now - and would need to be maintained if kept in future versions.
- stndDefined is schema-based & more extensible (& preferred?).
- Krystian Kedron Test with stndDefined Schema validation in ONAP VES collector has some issues:
- validates whole schema not just relevant part
- Some schemas are missing, & some schema in 3gpp forge are incorrect
- Martin Skorupski CM Notification: Sometimes hard to map CM change back to the Yang model for the change
- Martin Skorupski Similar for other VES messages - when referring to a managed object it is not clearly mandated how to map back to yang model.
- Krystian Kedron Currently ONAP PM Mapper does not support stndDefined ... all notifications mapped to perf3gpp messages
- Krystian Kedron Update of PM Mapper to VES 7.2:
- 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
- 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:
Update for ONAP Requirements Sub Committee
- Timo Perala, Alla Goldner : ONAP Requirements subcommittee request an update on areas where ONAP and O-RAN share interest.
- What is/are the area/s of common interest?
- What is the current state of affairs?
- What are the future topics to address?
- Any issues that require more emphasis from the community, or more formal collaboration relation between the two communities is needed?
- Anything else you think it worthwhile to highlight.
- Others presenting / providing input
- SMO deployment (Christophe)
- Slicing Use case (Ahila)
- ASD container / descriptor
- SON (Shankar)
- Update from OSC/ONAP alignment topics (from last presentation in Mar? 2021)
- Update from this meeting series: (Note this meeting series is informational/discussion only - refer to related decision fora for detail/reference)
- Some topics/headings discussed recently:
- Use cases / prototypes
- ONAP SON use case
- ONAP Slicing use case
- Sleeping Cell etc
- O1
- VES message formats
- CM, FM, PM (File), PM (Stream) etc
- CM yang model alignment
- FM / Alarm coordination
- VES message formats
- A1 Policy
- SMO Deployment (ONAP & OSC & other project's components)
- Test environments
- Simulators
- OSC O1 simulators (generic, O-RU, O-DU)
- OSC A1 simulator
- O1/A1 (Sleeping Cell) CNF simulator
- ONAP RAN simulator
- CNF packaging
- Topology
- Need for higher-level CM models - beyond canonical/spec models
- (later ... O2)
- Use cases / prototypes
- Need to re-stress the desire to have a Formal collaboration between OSC & ONAP, e.g. at requirements & TOC/TSC committee level
- 5G Super Blueprint initiative was proposed as a candidate to drive this, but different levels of engagement in ONAP vs OSC.
- Some topics/headings discussed recently:
Q&A:
- Ran out of time this weekONAP 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.
- https://wiki.onap.org/display/DW/Use+Case+Realization+Call%3A+Aug+23%2C+2021 (Continue from July 26 call https://wiki.onap.org/display/DW/Use+Case+Realization+Call%3A+July+26%2C+2021)