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
  • Meeting ID: 890 6970 8424
  • You will need a Participant ID so you will need to join the meeting from a Zoom client first to get this.
  • Dial in: (Local numbers)
    • +1 646 558 8656 US (New York)
    • +49 30 5679 5800 Germany
    • +49 69 3807 9883 Germany
    • +353 1 240 8941 Ireland
    • +46 8 4468 2488 Sweden
    • +46 8 5016 3827 Sweden
    • +358 3 4109 2129 Finland
    • +358 9 7252 2471 Finland

Date

Attendees

See also / co-located (ONAP/O-RAN-SC/SMO - Meeting)

Contents:


Recording

Notes:

Housekeeping:

  • Reminder from previous weeks:
  • 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)

SIM (Alex Stancu)

OAM (Martin Skorupski)

O-DU (HariomGupta(HCL))

  • 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.
    • Ref: https://jira.onap.org/browse/REQ-887
    • (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?)




1 Comment

  1. John Keeney  I'm working with Kenny Paulto get a bridge to kick off the ONAP special package for O-RAN meetings.