2023-02-01 Meeting notes - Joint OAM / NONRTRIC / SIM Community meeting
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
Please checkout the calendars:
Anti-Trust Notice
Date
Feb 1, 2023
Attendees
@John Keeney (Ericsson EST) (Ericsson EST & OSC NONRTRIC)
@Martin Skorupski (Highstreet & OSC OAM)
@James Li (CMTI & OSC INT)
@N.K. Shankaranarayanan (ONAP TSC)
@Halil Cakal (Ericsson EST)
@Kevin Timoney (Ericsson EST)
@Sonia Sangari (Ericsson EST)
@Carsten Höseler(TU-Dortmund)
Luiz Felizardo da Silva Neto
Joao Gustavo Rodrigues De Oliveira
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 2023-02-01 Meeting notes (ONAP/O-RAN-SC/SMO - Meeting)
Contents
Recording
Notes:
Housekeeping:
Calendar:
09:00 PST | 12:00 EST | 17:00 UTC | 17:00 GMT | 18:00 CET | 22:30 IST | 01:00 (+1d) CST
OSC SMO project calls now move to its own time slot - alternate Thursdays
See OSC RSAC Calendar: https://lf-o-ran-sc.atlassian.net/wiki/display/RSAC/calendars
See also OSC Meetings calendar: https://lists.o-ran-sc.org/g/main/calendar
(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 also OSC AIML Project meeting notes
OSC Project roundup:
News from OSC TOC call last week
https://lf-o-ran-sc.atlassian.net/wiki/display/TOC/#ORANSCTechnicalOversightCommittee(TOC)
Last week's TOC (Thursday):
No call last week
This week's TOC (Tomorrow):
No update.
NONRTRIC (@John Keeney (Ericsson EST))
G Maintenance Release - small bug fixes etc
As per last week. Development for each of the topics below continue ...
Release H Planning continues:
(R1) Service Exposure & Management
CAPIF Aligned Service Registry
Secured/Sandbox execution environment
Controlled access & exposure of service to/from rApps
(R1) Data Management & Exposure
Previous focus on PM data - but will extend to other use cases too
Aim to work with AIML project for Training (and Inference ?) data access
rApp Management
Built on ONAP “Automation Composition” model & platform to implement rApp use cases
rApp-specific extensions needed
Packaging, Onboarding & Orchestration of rApps
rApp-specific packaging & Onboarding
Aim to align with / inform ongoing work in O-RAN (& OSC) about Common App packaging & Onboarding.
(rApps with & without µService)
Overlap with Service Exposure work to examine role of an rApp Manager to support controlled exposure & LCM of µService and non-µService parts of an rApp
Continued A1-Policy & A1-Enrichment-Information evolution (& R1-A1)
A1 Spec evolution
A1-Policy work in ONAP (continues in ONAP London) - candidate for R1-A1(P)
A1-EI management as part of DME - candidate for how to include A1-EI in R1-DME
Sample use cases (rApps)
Requirements Drivers for rApp/R1 development
High degree of cross-project integration activity
Testing, Maintenance & Housekeeping
Function Test & Integration Test environment,
Support integration, deployment & configuration of SMO/Non-RT-RIC related functions & usecases in OSC Integration env.
Project coordination, Documentation, Delivery, Reporting, Cross-project alignment, Community demos, O-RAN Standardization support, etc.
SIM (@Alex Stancu)
No Update
OAM (@Martin Skorupski)
Investigating solutions for a Gateway in OAM Docker compose
Will consider Istio and Kong
O-DU (@Hariom Gupta @Vidhu (Deactivated))
No Update
OSC Integration / INT (@James Li )
Planning discussion with Windriver re X-Testing
RSAC/SMO (@David Kinsey [AT&T])
Ref: 2024 RSAC Meetings
Discussion on H Release Planning
Ongoing work in O-DU project
AI/ML platform project ()
Minutes & Meeting: Meeting notes
No update this week
ONAP Use cases (@N.K. Shankaranarayanan)
Long discussion last week!
TS 28.532 seems to indicate that a combination of href & path parameters should give enough info to extract objectClass and objectInstance of the source of any CM change.
Will update the sample message in https://jira.onap.org/browse/INT-2180 && https://jira.onap.org/browse/INT-2181
Work in ONAP CPS can be tracked at https://jira.onap.org/browse/CPS-1407 && https://wiki.onap.org/display/DW/CPS-1434%3A+VES+Message+to+update+CPS+DB
ONAP / OSC / O-RAN Alliance: Cooperation & Alignment
@N.K. Shankaranarayanan: Follow on from previous weeks: Lots of discussion at ONAP TSC.
No convergence yet, but lots of interest. Ref TSC Minutes: https://wiki.onap.org/display/Meetings/2023+TSC+MEETING+MINUTES
Will aim for cross-discussions at RSAC / ONAP-ReqSubCom level.
@Timo Perala will introduce ONAP-ReqSubCom at RSAC call next week - Discussed with @Former user (Deleted) & @David Kinsey [AT&T]
Questions / Comments / AOB:
@N.K. Shankaranarayanan Any update of getting PM data?
OSC SMO project have a VES collector which places messages in an InFluxDB - can be visualized.
OSC NONRTRIC project (DMaaP Adapter) allows DMaaP & Kafka messages be filtered & passed to subscribers (rApps) via ICS (Information Coordinator Server)
OSC NONRTRIC also Demonstrated File-based PM collection & filtering & delivery to subscribers (rApps) via ICS (Information Coordinator Server)
Also supports other types of data streamed from S3 data storage
Also experimenting with collecting any DMaaP/Kafka messages in InfluxDB using a Kafka Connector - not specific to VES messages.
No clear proposal for a coordianted/multivendor/spec'ed DME way to get data from datastore (e.g. influxDB)
Awaiting some more clarity for rApp subscribers/queries from R1 DME spec in WG2
Awaiting some clarity from WG10 about intra-SMO (inter SMOF) interfaces from WG10.
Meeting ends