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:

OSC Project roundup:

NONRTRIC (John Keeney)

  • OSC D Release ready. Branch & staging done.
  • Hoping to have a proposal on rApps & R1 in comining weeks.

SIM (Alex Stancu)

  • Ready for release. Branch done. 

OAM (Martin Skorupski)

  • Ready for release Branch done. 
  • user-4594e 's work on Adapter is added to D Release branch

OSC Release D Integration:

  • D Release delayed for another week. Vote at next week's TOC call
  • Alex Stancu OSC lab now supports IPv6 - but will not enable until after the D Release.
    • O-DU SIM now working with IPv4

O-DU (HariomGupta(HCL))

  • Testing D-Release currently - all working (IPv4)

ONAP Requirements Subcommittee

ONAP SMO deployment options (Christophe Closset (AT&T) & Amar Kapadia (AARNA))

  • Ref: to last 2 meetings.
  • Ref: Friday meeting Minutes & Recording from last week : https://wiki.onap.org/display/Meetings/2021-06-25+Meeting+notes)

  • INFO provided by from Christophe - 2021-06-30:  (Presented by Martial)

    Just a few notes:

    • We have agreed with ONAP and other members of O-RAN SC to keep an ad-hoc call on Friday to discuss technical details for now (will remove this meeting once all details are sorted out and use the joint meeting to report status)
    • Main comment from John is that we cannot consider an SMO deployment without having a way to deploy Non-RT-RIC as well as ONAP components (hence a debate on how this should materialize : extend OOM? )
    • We have progressed on the POC in the meanwhile, Sebastien had an idea and has pushed a small repository on github to show what we are doing for now to create a unique installation for O-RAN, trying to implement the following idea:
      • Started from IT/DEP repo, containing some Helm charts for ORAN (including Non-RT-RIC)
      • Seems an embryo of using ONAP charts to deploy SMO components but sounded like a fork of ONAP charts
      • Instead of copy pasting OOM charts, he create a git submodule referring to oom ONAP charts repo (to keep ONAP untouched)
      • Rework the ORAN charts to map them to the OOM structure (like OOM'ized O-RAN charts)
      • Try and build (created some makefiles, inspired from ONAP) then push them to a single chart repository
      • Merged ONAP override and ORAN override to have a single file
      • Created an Install script to deploy the charts in a single Namespace
      • … it worked more or less

    We plan to show that maybe on Friday call

  • Initial (private) Github repo to have info from both ONAP & OSC  - testing this approach.
  • No focus yet on CNFs etc yet.
    • Relationship with ONAP CNFs & O2 is not clear yet.

After the Call: ONAP Release progress (David McBride )

  • ONAP Intanbul M2 passed in ONAP TSC.