2024-06-04 Meeting notes - Joint OAM / NONRTRIC / SIM Community meeting
Time & Location:
Time Change: This meeting is now 1 hour later - 15:00 UTC on Tuesdays
Meeting Detail: Times & Joining Info
Today: Tuesday at 15:00 UTC (15:00 UTC in Winter Northern Hemisphere TBC)
https://us02web.zoom.us/j/89069708424?pwd=aGJOZm54eTUxd0FXR0VCU1N0ejBrUT09
Ensure you are signed into your Zoom account to join.
Meeting ID: 890 6970 8424. By Phone: Dial in (Local numbers): You will need a Participant ID so you will need to join the meeting from a Zoom client first to get this.
NOTE: During the "Daylight Savings Time" changeover periods (US vs Europe vs Asia) the time of the meetings may fluctuate.
Summer (norther hemisphere) (Q2 & Q3) time eventually stabilizes to:
8am PDT | 11am EDT | 15:00 UTC | 16:00 BST | 17:00 CEST | 18:00 EEST | 20:30 IST | 23:00 CST | +1d 00:00 JST (Wed)Winter (non-DST) (Q1 & Q4): TBC: Probably 8am PST | 11pm EST | 16:00 UTC | 16:00 GMT | 17:00 CET | 18:00 EET | 21:30 IST | +1d 00:00 CST (Wed) | +1d 01:00 JST (Wed)
Please checkout the calendars:
Anti-Trust Notice
Date
Jun 4, 2024
Attendees
@John Keeney (Ericsson EST)(Ericsson EST & OSC NONRTRIC)
@Martin Skorupski (Highstreet & OSC OAM)
@Alex Stancu (Highstreet & OSC SIM)
@subhash (Samsung & OSC AIMLFW)
@Varadarajan(Samsung)
@Aravindhan Ayyanathan (Ericsson EST)
@RAVITEJA KARUMURI (EST) (Ericsson EST)
@Denis G Noonan (Ericsson Software Technology) (Ericsson EST)
@Francesco Davide Lapenta (Ericsson EST)
@guru raja (Tech Mahindra)
May not have captured a full correct attendee list for this meeting ... please add/remove yourself
See also / co-located (ONAP/O-RAN-SC/SMO - Meeting)
Co-located with ONAP 2024-06-04 Meeting notes (ONAP/O-RAN-SC/SMO - Meeting) (Will add link when available)
Contents
- 1 Time & Location:
- 2 Anti-Trust Notice
- 3 Date
- 4 Attendees
- 5 See also / co-located (ONAP/O-RAN-SC/SMO - Meeting)
- 6 Contents
- 7 Recording
- 8 Notes:
- 8.1 Housekeeping:
- 8.2 OSC Project roundup:
- 8.2.1 News from OSC TOC & OSFG calls last week
- 8.2.2 NONRTRIC (@John Keeney (Ericsson EST))
- 8.2.3 SIM (@Alex Stancu)
- 8.2.4 OAM (@Martin Skorupski)
- 8.2.5 OSC Integration / INT (@James Li)
- 8.2.6 SMO (@Seshu Kumar Mudiganti)
- 8.2.7 RSAC (@David Kinsey [AT&T] @Rittwik Jana)
- 8.2.8 AI/ML platform project (@subhash )
- 8.3 ONAP Update (@N.K. Shankaranarayanan)
- 8.4 ONAP/OSC Usecases (@N.K. Shankaranarayanan)
- 8.5 Questions / Comments / AOB:
Recording
Notes:
Housekeeping:
Calendar:
No Meeting next week:
@Martin Skorupski is away & @John Keeney (Ericsson EST) has a conflict
Time Change:
This meeting is now 1 hour later - 15:00 UTC
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 & OSFG calls last week
TOC: https://lf-o-ran-sc.atlassian.net/wiki/display/TOC/#ORANSCTechnicalOversightCommittee(TOC)
Last week's TOC (Thursday):
Starting release preparations
Repo scanning to start this week
This week's TOC (in 2 days):
More Release Planning
OSFG:
Work on whitepaper continues - almost complete
Ready for review
NONRTRIC (@John Keeney (Ericsson EST))
Continuing tasks as mentioned previous weeks:
Kicking off Release preparation
Hopefully we will be on time for ONAP New Dehli & OSC J-Release
Continue work our new Service Manager function
Improving Documentation & deployment scripts etc
Lots still to do! Backlog will continue into next release
Continue work on rApp Manager - as a focal point for tying together alot of other existing activities
Working on some sample rApps. e.g. See Release J: Simple rApp using Hello World Microservice
Working on SME & DME integration & improvements
Continue maturing the A1-Policy Controller function (ref ONAP) - including a potential new NBI (v3) to achieve R1 alignment
Current API will be maintained but deprecated for several releases to come.
Making slow but steady progress.
First version of R1 API implemented
Lots of work on testing & benchmarking & documentation
Still need to get working on a proper A1-Policy Integration test with OSC near-RT-RIC (A1 Mediator)
No update from near-RT-RIC team
Also working on REST tracing in A1-Policy functions (currently in ONAP)
Will need to de-prioritise many of the older less-used NONRTRIC functions - we welcome others in the community to help take these on if interested.
Need to study how/if we can achieve R1-DME alignment. Specs continue to diverge from our implementation - with alot of effort need to align. We welcome contributors to help here.
SIM (@Alex Stancu)
Still updating SIM base platform - as per previous weeks.
Working with @Martin Skorupski on O-RU/O-DU
Release Preparation continues
OAM (@Martin Skorupski)
Cleaning up Jira tickets for J Release
Release Preparation continues
OSC Integration / INT (@James Li)
No update this week
SMO (@Seshu Kumar Mudiganti)
No update this week.
Meeting notes Meeting notes
Topology & Inventory Proposal:
@John Keeney (Ericsson EST) First version of seed-code is now being reviewed by @Seshu Kumar Mudiganti
Hope to do a review during SMO call this week (tomorrow)
RSAC (@David Kinsey [AT&T] @Rittwik Jana)
No update this week
Minutes: 2024 RSAC Meetings
AI/ML platform project (@subhash )
Minutes & Meeting: Meeting notes
@subhash
Integrated Pipeline Mnagement is not ready yet - will move to next release
Upgrading platform
K8s → 1.28
Trying to remove docker dependencies
Can we start using NONRTRIC Service Manager to expose AI/ML Platform functions?
Yes. The Service Manager is now enabled as part of the smo-install and nonrtric-install charts in it/dep.
We can add those endpoints AI/ML services as part of a bootstrap process, or add them during smo-install scripts, or can be added as part of AI/ML framework install scripts/charts.
Currently there is no enforcement of service exposure/access - but we want to use Service Manager (R1-SME) as the 'right way' to expose services to rApps and enable rApps to get access to them.
Currently doesn't matter if service is in a different cluster - later may need to create a tunnel or inter-cluster mesh to enforce exposure - but OK for now.
@John Keeney (Ericsson EST) will forward some links to @subhash, and hopefully in the next few days we'll have examples of existing services being added into the Service Manager registry as SMO start-up time.
@John Keeney (Ericsson EST) & @subhash Will work on some rApp use cases for next release that use training.
ONAP Update (@N.K. Shankaranarayanan)
No update this week
ONAP/OSC Usecases (@N.K. Shankaranarayanan)
No update this week.
Questions / Comments / AOB:
Updates/Questions in NONRTRIC @guru raja
How to use DMaaP adapter for Bulk PM
@John Keeney (Ericsson EST) : Don't. Please use the RAN-PM functions which are much more functional & specific for bulk-PM.
https://docs.o-ran-sc.org/projects/o-ran-sc-nonrtric-plt-ranpm
RANPM charts are not yet integrated into smo-install charts
Integratin between SME & Keycloak
Current integration between CAPIF & Keycloak is not the correct way for rApps.
Hope to work on this (including exposure enforcement) in furhter releases - but resourcing is not certain yet. May need to wait for community engagement here to help out.
Meeting ends 32 min