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)

  • Working hard on integration & documentation tasks now that OSC M4 date has passed.
    • ReadTheDocs Documentation esp. is very out of date!
  • ONAP A1 Policy Functions - need to wrap M1 tickets for ONAP I.
  • John Keeney Martin Skorupski Alex Stancu, Felix & Mahesh  - Hope we can catch up to figure out our way through the e2e integration tasks for OSC D release
    • Will discuss initially at RSAC call tomorrow (20 May)

SIM (Alex Stancu)

OAM (Martin Skorupski)

  • Working on docker compose for SMO test environments 
  • Has several docker-compose files for different deployments etc

O-DU (HariomGupta(HCL))

  • Commit ready for review/merge.

CM Notifications in ONAP

  • Marcin Wilk: Is anyone in SDNR/CCSDK/OSC working on CM Notifications?
    • Martin Skorupski lots of work on VES - esp faults & netconf call home
    • Damien from DCAE project also in Guilin worked on newer functions in VES to support this & collction to DMaaP
      • Marcin has verified this worked
    • NK Shankar: Some work ongoing for this in the ONAP OOF SON use case (Calls Friday 9:?? EST for more info)
      • For OOF SON use case - CM notifications for CPS - part of CCSDK - used in SDNR
      • Events come from RANSIM simulator
      • Sandeep Shah Working on this.  JIRA: https://jira.onap.org/browse/CCSDK-3296
      • Still figuring out how exactly to do this with VES etc - but work is ongoing.

Helm charts / Docker Compose etc

  • John Keeney working on Docker-compose & helm charts for OSC D +
  • Want to have BOTH docker-compose and helm charts for deploying functions. Martin Skorupski Good idea - means dev & release versions can evolve independently & lots of different configurations etc.
    • John Keeney Will maintain both ... and each function in nonrtric have their own docker images - and are pretty standalone - so are easiy to deploy individually or in different combinations.
  • John Keeney Would like to maintain multiple flavours of helm charts for nonrtric in nonrtric repo, and then reuse in IT/DEP.
    • But we need to be very careful that we actually manage to have a test-environment integrated deployment at release times.
  • John Keeney Reminded the OSC TOC today that it was previously discussed adding PTLs as committer in the IT/DEP repo - to help Felix & avoid bottleneck. Will hopefully happen soon in coming days.


How do we refer to or position or differentiate between SDNC / SDNR / NONRTRIC / SMO etc

  • Question by NK Shankar
    • John Keeney We don't - it depends on your perspective.
    • OSC:   
      • OAM, NONRTRIC and SMO are all different projects in OSC only
        • OAM mostly reuses software from ONAP - main focus OAM & O1 - software comes from DMaaP, DCAE CCSDK/SDNR in ONAP.
        • NONRTRIC Has multiple functions (see Release D - DRAFT) - only A1 Policy functions are taken from ONAP CCSDK - all rest are developed in OSC.
          • Focus on functions for A1 Policies, A1 Enrichment, R1, RApps. Plus control panel & A1 Simulator
        • SMO project currently  develops new functions for OAM - not from ONAP
    • ONAP
      • There is no concept of SMO or NONRTRIC in ONAP - these are OSC concepts
      • Lots of functions in ONAP that can be useful for an SMO (especially in CCSDK for O1 & A1 Policies)
      • Ref also SON & Slicing use cases in ONAP that touch on ORAN related concepts.
    • It is hoped that functions can be mixed & matched as a need arises - and hopefully we can stay aligned & support resue - which is one of the main focus of this meeting series!
    • NK Shankar - looking forward to use cases & reusing concepts - not sure yet how/where work will be homed if in ONAP - Martin Skorupski Lets use this meeting series to get such discussions straight!
    • William DIEGO - Introduced - As an OSC TOC member will help liaise between OSC & ONAP - from OSC
    • Timo Perala Chaker Al-Hakim will help out from ONAP side (TBC as replacement for Swaminathan Seetharaman)

O-RAN F2F - 01-14 June 2021

  • No update

ONAP Q/A

  • no other topics today