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

Please checkout the calendars:

Date

Attendees

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

Contents

Recording

Notes:

Housekeeping:

OSC SMO Meeting Series: Reminder from previous weeks:

OSC Project roundup:

News from OSC TOC call this week

NONRTRIC (John Keeney)

  • E-Maintenance Release
    • A1-Policy Management Service
      • Removing deprecated V1 A1-PMS API & CBS/Consul configuration
      • Removing capability to configure using ONAP CBS/Consul
    • Couple of typos/Bugs etc - especially version numbers in test/integration charts
    • Updated 3PPs
  • Proposal: Splitting gerrit/repo contents across multiple repos
  • David Kinsey What would rApp descriptor look like?, used during registration, describing required/provided service, required/provided data etc.
    • WG10 needs to move forward on this re. App LCM, requested by WG2 to present a proposal for rApps.
    • OSC NONRTRIC likely has opinions
    • Overlap between packaging & modelling - discussions ongoing
      • Where would this information go in the model?
      • Already have some input from WG6
    • Need to be careful about difference between CNF, Microservice, xApp, rApp etc.  e.g. extend ASD descriptor (but ASD focuses just on K8S as yet)? 
    • OSC NONRTRIC approach 'til now has been to focus on App LCM & management post-onboarding - leveraging ONAP Control Spec - starting at the 'bottom'
      • Need to work up the chain, while WG10 team seems to be working from opposite direction re Common Apps ... still need to meet in the middle. 

SIM (Alex Stancu)

  • No update
  • No Maintenance Release

OAM (Martin Skorupski)

O-DU (Hariom Gupta Vidhu Shekhar Pandey)

  • No update
  • David Kinsey : Likely need to extend O1 data reporting schema etc (Aligning with 3GPP)

RSAC/SMO (David Kinsey)

  • RSAC (David Kinsey) F-Release Requirements:
    • Want OTF scripts for releases / integration tests (from each project)
      • Each project needs to provide OTF inputs
      • Will shorten release overhead
      • Need a combination of OTF & the Integration team's work on PythonSDK for scripts/overrides etc to roll use-case-specific integration environment setup (Christophe & Sebastien)

OSC Integration / INT (James Li )

  • See above (RSAC) re use of OTF for Integration tests / release
  • NONRTRIC team to update James Li for any maintenance release updates (e.g. versions etc.)

O-RU/O-DU Front-haul Recovery (Hello World) rApp not working

LFN DTF Presentation: "RAN Simulation for ONAP and OSC Use Cases"

SMO Integration Charts (Sebastien Determe)

  •  E(-Maintenance)-Release Testing continues - v. nearly all working now.
  • Gervais-Martial Ngueko : Is this work still aligning with OSC goals?:
    • Probably need align a little more with OTF ... but still the right direction

ASD Orchestration

ONAP Use cases etc (N.K. Shankaranarayanan)

  •  postponed

Q/A

  •  postponed