2022-01-19 Meeting notes - Joint OAM / NONRTRIC / SIM SCRUM 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:
Date
Jan 19, 2022
Attendees
@John Keeney (Ericsson EST) (Ericsson EST & OSC NONRTRIC)
@Martin Skorupski (Highstreet & OSC OAM & ONAP)
@Alex Stancu(Highstreet & OSC SIM)
@David Kinsey [AT&T] (AT&T & OSC RSAC)
@James Li (CMCC & OSC INT)
Arnold Alvarado (NIWC)
@David Allabaugh (Fujitsu)
Dilip Krishnaswamy (STL)
@Kevin Tang (STL)
@Kevin Timoney (Ericsson EST)
@marcin krasowski (Samsung)
@Gervais-Martial Ngueko (AT&T)
Mateusz Zawadzki (Samsung)
Michal Cmarada (Pantheon)
@N.K. Shankaranarayanan (STL)
@Pawel Slowikowski (Samsung)
@Sonia Sangari (Ericsson EST)
Sebastien Determe (AT&T)
@Timo Perala (Nokia) (Nokia)
@Former user (Deleted) (Fujitsu)
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 2022-01-19 Meeting notes (ONAP/O-RAN-SC/SMO - Meeting)
Contents
- 1 Date
- 2 Attendees
- 3 See also / co-located (ONAP/O-RAN-SC/SMO - Meeting)
- 4 Contents
- 5 Recording
- 6 Notes:
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://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.
OSC Project roundup:
News from OSC TOC call this week
https://lf-o-ran-sc.atlassian.net/wiki/display/TOC/#ORANSCTechnicalOversightCommittee(TOC)
E-maintenance Release
Some O-DU-High functions ready for release
NONRTIC will try get ODU Slice Assurance use case extended to work with this
(@David Kinsey [AT&T] Issues with Bedminster lab ... so this might be delayed)
NONRTRIC (@John Keeney (Ericsson EST))
E-Maintenance Release
A1-Policy Management Service
Removing deprecated V1 A1-PMS API & CBS/Consul configuration
Removing capability to configure using ONAP CBS/Consul
Couple of typos/Bugs etc - especially version numbers in test/integration charts
Updated 3PPs
Proposal: Splitting gerrit/repo contents across multiple repos
@David Kinsey [AT&T] What would rApp descriptor look like?, used during registration, describing required/provided service, required/provided data etc.
WG10 needs to move forward on this re. App LCM, requested by WG2 to present a proposal for rApps.
OSC NONRTRIC likely has opinions
Overlap between packaging & modelling - discussions ongoing
Where would this information go in the model?
Already have some input from WG6
Need to be careful about difference between CNF, Microservice, xApp, rApp etc. e.g. extend ASD descriptor (but ASD focuses just on K8S as yet)?
OSC NONRTRIC approach 'til now has been to focus on App LCM & management post-onboarding - leveraging ONAP Control Spec - starting at the 'bottom'
Need to work up the chain, while WG10 team seems to be working from opposite direction re Common Apps ... still need to meet in the middle.
SIM (@Alex Stancu)
No update
No Maintenance Release
OAM (@Martin Skorupski)
No Maintenance Release issues
- DCAEGEN2-3024 - Support of values with 'oneOf' types. Closed
O-DU (@Hariom Gupta @Vidhu (Deactivated))
No update
@David Kinsey [AT&T] : Likely need to extend O1 data reporting schema etc (Aligning with 3GPP)
RSAC/SMO (@David Kinsey [AT&T])
RSAC (@David Kinsey [AT&T]) F-Release Requirements:
Want OTF scripts for releases / integration tests (from each project)
Each project needs to provide OTF inputs
Will shorten release overhead
Need a combination of OTF & the Integration team's work on PythonSDK for scripts/overrides etc to roll use-case-specific integration environment setup (Christophe & Sebastien)
OSC Integration / INT (@James Li )
See above (RSAC) re use of OTF for Integration tests / release
NONRTRIC team to update @James Li for any maintenance release updates (e.g. versions etc.)
O-RU/O-DU Front-haul Recovery (Hello World) rApp not working
Endpoint used by rApp (/rests/data/network-topology:network-topology/topology=topology-netconf/node=[O-DU-ID]/yang-ext:mount/o-ran-sc-du-hello-world:network-function/du-to-ru-connection=[O-RU-ID]) is deprecated & will be removed.
Updated in E-Release with O-DU Slicing use case updates
rApp & test stubs needs to be updated
Integration environment for this use case is currently broken ...
@John Keeney (Ericsson EST) Will work on this immediately ... hopefully fixed by E-Maintenance
@Martin Skorupski @Alex Stancu @John Keeney (Ericsson EST) @Xue Gao will discuss offline
LFN DTF Presentation: "RAN Simulation for ONAP and OSC Use Cases"
Presentation at LFN vDTF:
SMO Integration Charts (Sebastien Determe)
E(-Maintenance)-Release Testing continues - v. nearly all working now.
@Gervais-Martial Ngueko : Is this work still aligning with OSC goals?:
Probably need align a little more with OTF ... but still the right direction
ASD Orchestration
(@43:00 in recording)
@David Kinsey [AT&T] PoC in ONAP for ASD Orchestration. Would be good to keep aligned.
When would be the right time to test/integrate/reuse/leverage in OSC ?
Best to reuse ONAP work, not re-invent
Need to examine how much other ONAP functionality is needed if reused in OSC (e.g. SDC, SO, etc)
Interesting to see the overlaps/requirements etc with multiple approaches for CNF-Orchestration & App-Orchestration are all examined
VNFs, CRDs, ASDs,
Would be good to get input from the ONAP PoC team.
@John Keeney (Ericsson EST) Ref discussions at LFN DTF on ASDs & ASDs in ONAP:
@David Kinsey [AT&T] Will create a wiki page to identify dependencies, opportunities, etc.
See also discussions in WG10 AppLCM (members)
Would be best to have use cases to drive forward discussions.
ONAP Use cases etc (@N.K. Shankaranarayanan)
postponed
Q/A
postponed