17:00 UTC, 09:00 PST, 12:00 EST,  17:00 GMT, 18:00 CET, 19:00 EET, 22:30 IST, 01:00 CST (Thurs), 02:00 JST (Thurs)


ZOOMhttps://us02web.zoom.us/j/89069708424?pwd=aGJOZm54eTUxd0FXR0VCU1N0ejBrUT09
Meeting ID: 890 6970 8424


Calendars:

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)

Table of Contents

Attendees

Informed

Discussion items

TimeItemWhoNotes
00:00Admin

Next meetings: 

2021-12-08: John Keeney 
2021-12-15: Martin Skorupski  (John might be ooo)
2021-12-22: canceled
2021-12-29: canceled
2022-01-05: canceled
2022-01-12: Martin Skorupski 

00:05O-RAN-SCO-RAN-SC PTLs

O-RAN-SC ToC


Projects:
  • Non-RT-RIC: John Keeney
    • link monitor rApp for slicing use case - issue 3gpp model vs O-RAN-SC model and VES stndDefined vs modified-ves-measurement-domain
    • hard-coded values for slice ids.
  • SIM: Alex Stancu
    • finalizing the release, int and documentation
  • OAM: Martin Skorupski
    • Q/A
    • finalizing the release, int and documentation
  • O-DU:HariomGupta(HCL) / @Vidhu.  
  • RSAC/SMO: @Rittwik
  • INT: James Li
    • work with each project PTL 
      • sec scan
      • license scan
      • branching
      • e-release page to doc achievements (RASC, how to do ....)
    • non-rt-ric and near-rt-ric integration in Taiwan lab
      • including xApps
    • prime lab is the Bedmister lab.
    • Question:
      • deployment used by INT projects (topic for RASC)
      • use case specific scenarios (deployments with different configs) in a single INT environment?
00:20SMO/Integration package/charts

ONAP Gerrit

O-RAN-SC Gerrit - MERGED

ongoing work


00:40ONAP Use casesN.K. Shankaranarayanan 

Shankar created a JIRA 
DCAEGEN2-2987 - Getting issue details... STATUS  
as a placeholder to converge on VES formats for SON use case.

Target: Jakarta on the Agenda tomorrow 12:00 UTC 

00:50O1 Models for R1

Shankar submitted a contribution to O-RAN WG2 on the notion of primary and secondary yang models. 2021-11-24 is a holiday and so I have he requested that it be on the agenda on Dec 9 WG2 meeting. The WG2 chairs said ok.

primary (O-RAN YANG) vs secondary yang (augmenting and representation of more efficient processing on SMO/ONAP level and whatever is needed  - in short: if the use case needs something in CPS which is not in the primary yang)

Question: sync between nodes in a transaction - example rollback. 

00:50LFN-developer-testing-forumTimo Perala 

Encouraging submissions to LFN DTF event in 10-13 Jan 2022. Call open now - Dec 3rd (ish (smile)).

Init proposal to be submitted by Shankar

01:00End





00:xx

O-RAN SC: Copying/Releasing helm charts in O-RAN-SC nexus repo

https://jira.linuxfoundation.org/plugins/servlet/theme/portal/2/IT-22586 (maybe restricted access?!?!)

Status: canceled (Nexus does not support Helm chart distribution)

Question from O-RAN-SC to ONAP: What is possible in ONAP nexus?

Sébastien Determe: adds some info

Idea: store the artifacts - instead of helm -  RELENG-3837 - Getting issue details... STATUS

Christophe Closset: ONAP on the way to move for helm charts to gitlab....



Action items