Time & Location:

New Meeting Slot

Have now moved to new meeting slot Wednesdays at 16:00 UTC!

https://zoom.us/j/436210993

NOTE: During the "Daylight Savings Time" changeover periods (US vs Europe vs Asia) the time of the meetings may fluctuate.

See the Calendar: (https://lists.o-ran-sc.org/g/main/calendar) 

Daylight Savings time changes have now completed for a few months so Summer meeting times are

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) 

See also:

Recording

Date

Attendees

Notes:

Housekeeping

  • For future meetings, for security reasons LF & LFN insist on passwords and/or attendees must be explicitly admitted - Already use this approach
  • Minutes will also be maintained in ONAP wiki at https://wiki.onap.org/pages/viewpage.action?pageId=24641575 - under the "Requirement Subcommittee" branch

Meeting Structure & Scope

  • John Keeney Concerns that scope might be too much for a single meeting, but we'll try, and if needed please re-raise this concern again
  • Scope:
    • OSC: Joint Community meeting for OSC OAM, NONRTRIC, SIM & SMO projects
    • OSC: Alignment between OSC OAM, NONRTRIC, SIM & SMO projects
    • Alignment & collaboration between OSC & ONAP
    • Alignment between ONAP & O-RAN

ONAP - ORAN harmonization

  • See new ONAP location for this (co-located) meeting https://wiki.onap.org/pages/viewpage.action?pageId=24641575  (See housekeeping above)
  • Swaminathan Seetharaman Michela Bevilacqua Martin Skorupski Will try to assemble list of relevant requirements and usecases in ONAP Guilin and ONAP Honolulu for later discussions - to use as a basis for alignment discussions.
  • ODL
  • Simulators (& see SIM section below)
    • Simulator used in ONAP for Slicing Usecase (WIPRO?) - but this is not a deployment simulator - runtime only.
    • Samsung demonstrated a nearRTRIC simulator - combining OSC A1 SIM and netconf endpoint.
    • O1 simulator - based on netopeer available in Lab (see point in SIM below)
  • Swaminathan Seetharaman ONAP Slicing Usecase already has a weekly ONAP-ORAN alignment meeting on Thursdays - (follow up)
  • Some discussion of components references in pic OAM Architecture#IntegrationintoSMO
    • OOF, Policy, SO and many other parts are not currently included in OSC SMO (ONAP deployment)
    • Not currently using OOM - will hopefully move to OOM soon.
    • SDNC provides O1 CM termination - A1 controller is separate in Bronze. - Will merge in Cherry+
    • DCAE is available for VEST & data collectors.
    • Unsure of plans to include AAF, Logginc, etc
    • Portal is included (NONRTRIC control panel & nearRTRIC portal)
  • Swaminathan Seetharaman Significant overlap with ONAP OOF usecase. Good possible candidate for A1/O1 alignment use case in ONAP. Also a good candidate for alignment wrt rApps.


NONRTRIC

  • Lasse Kaihlavirta John Keeney past issue with updating Config Maps without K8s pod restart is confirmed in ONAP.
    • Issue does not exist in OSC deployment
    • Samsung also have internal ONAP-like charts that do not have the issue
    • Issue is caused by OOM
      • Will work on this offline

SIM

  • Alex Stancu
    • Now has access to OSC T-Lab environment. For others to get access contact Felix Zhe Huang
    • Lab is the main integration
    • Mahesh Jethanandani now has a VM there for testing O1-CM YANG models. Postman scripts will be made available to access simulator.
    • All current instructions for accessing the lab are Windows-based ... working on getting connected from other OSes
    • Martin Skorupski Still working on getting access to/from Winlab lab.
  • OTF Alex Stancusubhash kumar singh