2020-10-28 Meeting notes - Joint OAM / NONRTRIC / SIM / SMO SCRUM meeting

2020-10-28 Meeting notes - Joint OAM / NONRTRIC / SIM / SMO SCRUM meeting

Time & Location:

New Meeting Slot

New Meeting Slot

We have now moved to new meeting slot Wednesdays at 16:00 UTC in Summer (DST), 17:00 UTC in Winter !

https://zoom.us/j/436210993

NOTE: During the "Daylight Savings Time" changeover periods (US vs Europe vs Asia) the time of the meetings may fluctuate. See the Calendar: (https://lists.o-ran-sc.org/g/main/calendar

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)

See also:

Recording

 

Date

Oct 28, 2020

Attendees

  • Sorry - attendee list not available for this meeting

Notes:

  • Time change:

    • Meeting time slot will change with DST changes - Summer 16:00 UTC, Winter 17:00 UTC.

    • During DST changeover peiod there may be some variability depending on how DST is handled in your area.

    • Many attendees (from Asia especially) come from regions that do not use DST - so local time will change in Winter/Summer. (Sorry )

    • Please keep an eye on the OSC calendar https://lists.o-ran-sc.org/g/main/calendar and ONAP calendar https://lists.onap.org/g/onap-meetings/calendar - we will work hard to keep all calendars consistent and accurate.

  • 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)

OSC Project roundup

NONRTRIC (@John Keeney (Ericsson EST))

  • Still working on A1 Enrichment Information coordination function & GUI for this

  • A1 v2.0 - extending Simulator & tests

  • rApp catalogue - test stub - almost ready

SMO (@Mahesh Jethanandani)

  • See later about app packaging

    • Continuing to test and build an app package format based on ONAP packaging format.

  • Working with @Alex Stancu  on test infrastructure for trying out O1 models 

    • @santanude has made postman scripts avialalble in SMO repo

SIM (@Alex Stancu )

  • O1 test infrastructure (above) available in Bedminster OSC lab

  • Still does not see how to continue wrt publishing/linking to 3GPP models.

    • Only using the models - but v.hard to not "copy" or "re-distribute" - will continue to try figure this out - this has been going on too long.

OAM (@Martin Skorupski )

  • Not alot to report

    • reviewing some o-du changes.

 

ONAP - OSC

  • ONAP Calendar - updated by @Swaminathan S

 

ONAP Guilin Useacases: Where do we need alignment & chance for collaboration (@Swaminathan S ) https://wiki.onap.org/display/DW/5G+Use+Cases+in+R7+Guilin?src=contextnavpagetreemode

  • OOF SON usecase:

    • Should align with O1 CM models / Yang. Current use bbf models. Want to use 3GPP/O-RAN models.

      • Will models become aviallable? @Martin Skorupski - Models are available from 3GPP, but sharing in O-RAN is difficult. Difficult to know if O-RAN models will be released in Nov. Train.

      • Depends on Honolulu release timeframe - November train versions would not be available until January?

      • Draft O-RU model already available.

    • @Sandeep Shah near-RT-RIC model? - Still ongoing & under discussion.

  • Slicing usecase

    • Mostly O1 focussed now

      • Would be good to use A1 instead - currently using handcrafted O1

    • Have a weekly O-RAN call already.

    • @Sandeep Shah O2 spec? Would be nice for slicing use case etc. - Not published yet.

    • Notification alignment needed.

    • Also considers transport

  • A1 Adapter

    • @John Keeney (Ericsson EST) In Honolulu will move beyond A1 Adapter - will examine A1 Policy Management & role for rApps R1 etc. Still have alot to do with normal continuing improvements & maturing functionality.

    • Want to focus on use cases too

  • Bulk PM

    • Fully aligned right now.

  • C&PS

    • Model-driven so should be directly reusable in OSC?

    • SON is a driving use case here.

  • VES Alignment

    • Clear how to proceed here. Just need to keep going.

 

OSC / ONAP alignment

  • @John Keeney (Ericsson EST) We need frank & open discussions at leadership level to drive collaboration

  • @John Keeney (Ericsson EST) @Sandeep Shah @Swaminathan S Perhaps should focus on Honolulu / cherry-dawn usecases for overlap. 

 

NONRTRIC / ONAP A1 PMS - Issue with dynamic confinguration updates

NONRTRIC - DMAAP etc: @Kuldeep Singh Negi (Deactivated)

App packaging @Mahesh Jethanandani

  • Ran out of time. Will cover next week