2021-06-16 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
Date
Jun 16, 2021
Attendees
@John Keeney (Ericsson EST)
@Martin Skorupski
@Alex Stancu
@Andrew Lamb
@Former user (Deleted)
@Dibas Das
Gervais-Martial Ngueko (AT&T)
@Hariom Gupta (Deactivated)
N K Shankar
@Manoj Nair
@Pawel Slowikowski
@Scott Blandford
@Sonia Sangari
@Timo Perala (Nokia)
@Vidhu (Deactivated)
@William DIEGO
Sorry - didn't manage to get a full attendees list for this meeting ... please add/remove yourself
See also / co-located (ONAP/O-RAN-SC/SMO - Meeting)
Co-located with ONAP 2021-06-16 Meeting notes (ONAP/O-RAN-SC/SMO - Meeting)
Contents:
Recording
Notes:
Housekeeping:
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
(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.
O-RAN has declared that recording are kept for 2 weeks only. Does this apply to us?
Is this a requirement, a privacy issue or a cost issue?
Not sure - the recording storage quota that we use is currently full - so we may need to delete old cloud recording?
All past recording are also available as files uploaded to the wiki pages - May be a storage issue later, but no plans to delete as yet.
OSC Project roundup:
NONRTRIC (@John Keeney (Ericsson EST))
As per last week:
Working hard on integration & documentation tasks now for OSC D release
@John Keeney (Ericsson EST) @Martin Skorupski @Alex Stancu - Will have a quick chat about double-checking integration environment. Looks good!
@John Keeney (Ericsson EST) Brief feedback of what happened at OSC TOC call this week: https://lf-o-ran-sc.atlassian.net/wiki/display/TOC/#ORANSCTechnicalOversightCommittee(TOC)-20210616 (Minutes not yet updated at time of writing)
Should soon have access to the it/dep
Need to push on with D Release task
Release E planning will start at RSAC tomorrow.
SIM (@Alex Stancu)
OSC Lab Integration environment is up & running now
Includes OAM, ONAP-SMO components, NONRTRIC and SIM components.
See Closed Loop Use Case Testing & https://gerrit.o-ran-sc.org/r/c/oam/+/6238
OAM (@Martin Skorupski)
Working on deployment & integration & OSC lab setup.
Some updates required with certs etc when using ONAP Honolulu functions using OOM (& some chart updates)
See slack channel https://onapproject.slack.com/archives/CLF0KRNKF/p1623835991081200 ?
@Former user (Deleted): NF-OAM-Adapter making good progress and finally running
O-DU (@Hariom Gupta (Deactivated))
OSC Lab & local testing
Is integration environment IPv6 only? Working on a small issue with IPv6 now.
Issue with checking/waiting of SMO is up & running when O-DU comes up (ves:pnfRegistration event may be ignored, or should be sent in a loop? SIM just once? Multiple events is no harm.)
May need to a timed loop to keep checking (e.g. every minute?). Not a great solution but prob OK for the Release D use case.
In OSC lab the SMO will already be running.
If NetConf client is up before O-DU it will keep trying until Netconf port is open.
(Best to only open the port when the O-DU is ready? Best to send ves:pnfRegistration event only when O-DU is up?)
Should discuss in RSAC.
... may need to do some more testing of these edge cases ....
Ongoing discussion over email about how OTF starts (configures? ) the O-DU high.
ONAP SMO deployment options (Christophe Closset (AT&T) & @Amar Kapadia (AARNA))
REF: Last week Proposal for an ONAP deployment specific for an ORAN SMO
Christophe not available to join this week - Hopefully we can discuss a little more next week.
(After the call ended: Martial: Further discussions for this ONAP PoC could happen at this call? Will be a few weeks before this proposal is presented to ONAP Arch. & Req committees etc, then ONAP TSC?)