2021-08-11 Meeting notes (ONAP/O-RAN-SC/SMO - Meeting) - Agenda

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?!?!)

Topic was discussed in DCAE Meeting: 2021-08-04 DCAE Meeting Notes

HV-VES vs "standard" VES collector

info: HV-VES not used by OOF-SON use case (yet)

info: no relation between HV-VES and PM-Mapper

2021-08-11 user-7f92d

I refactored current Jira’s base on our discussion:

• https://jira.onap.org/browse/DCAEGEN2-2873 (bug)
• https://jira.onap.org/browse/DCAEGEN2-2874 (VES 7.1 enhancements)

And also create a new one:

• https://jira.onap.org/browse/DCAEGEN2-2880  (support for VES 7.2)

Meeting? on Friday 6/25

https://lists.onap.org/g/onap-meetings/viewevent?repeatid=37969&eventid=1192141&calstart=2021-06-25

• • https://lists.onap.org/g/onap-meetings/viewevent?repeatid=37969&eventid=1192141&calstart=2021-06-25 bhanu chandra
  • https://wiki.onap.org/pages/viewpage.action?pageId=103422272
    • (Updated afterward: Minutes & Recording: https://wiki.onap.org/display/Meetings/2021-06-25+Meeting+notes)
• proposed by aarna
• see email - TODO add link to wiki
• proposal to use this time slot here

Activity

• kubernetes updates
• issues with certs addressed
• reuse of O-RAN-SC helm 
• Winriver lab

<Martin Skorupski needed to leave. John Keeney continues minutes. See also: 2021-06-23 Meeting notes - Joint OAM / NONRTRIC / SIM SCRUM meeting >

• REF: 2 Weeks ago: Proposal for an ONAP deployment specific for an ORAN SMO
  • Ref: https://jira.onap.org/browse/REQ-887
• @Christophe : Meeting upcoming
  • Every Friday: 
    
    • https://lists.onap.org/g/onap-meetings/viewevent?repeatid=37969&eventid=1192141&calstart=2021-06-25 bhanu chandra
    • https://wiki.onap.org/pages/viewpage.action?pageId=103422272
    • (Updated afterward: Minutes & Recording: https://wiki.onap.org/display/Meetings/2021-06-25+Meeting+notes)
  • Attempting to replicate functionality in OSC OAM/NONRTRIC/SIM demo - based on OSC charts.
    • Mainly updating charts etc.
    • Certs need updating
  • Will be testing in ONAP WindRiver lab - setup etc.   Might be a good place to collaborate.
•  John Keeney Any update on how to reuse OSC & other external components?
  • @Christophe, will be challenging in OOM, & need to reuse structure & some charts from OOM
• John Keeney Any ideas where SMO would be different from "Full ONAP"
  • @Christophe: Plan to start with OSC charts/flavour ... then depends on Usecases ...
  • Hope to be able to make use of the override files to create different flavours .. aiming for something similar to OSC version
    • Ref Closed loop use case & "D" Release - Closed Loop Use Case: Simulation of O-RU and O-DU & "D" - Closed Loop Use Case 
• John Keeney Probably need different versions for different usecases
  • @Christophe ... OOM have this same idea to have multiple flavours.  Discussion gets broader when non-ONAP components are added.
• @NK Shankar ... Should also consider SON and Slicing usecases.
• John Keeney Recall that the OSC D release usecase is not real world ... and will mature in coming releases. Currently mostly treated as an integration requirements driver
  • Ref Closed loop use case & "D" Release - Closed Loop Use Case: Simulation of O-RU and O-DU & "D" - Closed Loop Use Case 
• @Christophe @NK Shankar Need to consider diversity of DCAE components used.  Also need to figure out how different simulators could co-exist.
• Lets continue discussions on Friday Call?

INFO from Christophe - 2021-06-30:

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 O-RAN (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 O-RAN 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 O-RAN 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 (https://wiki.onap.org/pages/viewpage.action?pageId=103422272)

--

Are the following pages related?

• CNF/VNF deployments

• https://wiki.onap.org/display/DW/Orchestration+Scenarios
  • https://wiki.onap.org/display/DW/O-RAN:+ASD+solution

2021-07-07:

way forward

• release helm repo by OOM should be created
  • (Added later: John Keeney Also asked about getting a helm chart repo for OSC.  https://lists.o-ran-sc.org/g/discuss/message/331)
• demo was shown last Friday how it could look like
• next step
  • sample overwrite files
• if access to the "demo git" is required, please reach out to Christophe Closset Sébastien Determe Gervais-Martial Ngueko

2021-07-14:

• https://github.com/gmngueko/oran-deployment/pull/1
• in non-overwrite helm only docker from "released" nexus should be included...

2021-07-21:

• from John Keeney LFN ticket required to put helm into nexus
• control about helm from different project

2021-07-28:

• not much additional features required for SMO deployment.
• next step in the area of CNF deployment in combination with SMO
  • as demoed one year ago by Samsung (including closed loop and A1 Policies)
  • use case will be updated to Honolulu 

2021-08-04:

• no updates on last weeks call
• cnf deployment - reuse of existing use case implementation.

The following 3GPP CM notifications specified in 3GPP TS 28.532 [4] are supported in O-RAN:

 notifyMOIAttributeValueChanges

 notifyMOICreation

 notifyMOIDeletion

 notifyMOIChanges

Its syntax is defined in

~/_3gpp/MnS ((SA88-Rel16))

└─ $ ▶ grep -anri notifyMOI*

OpenAPI/provMnS.yaml:87:        notifyMOICreation:

OpenAPI/provMnS.yaml:95:          $ref: '#/components/schemas/notifyMOICreation-NotifType'

OpenAPI/provMnS.yaml:108:       notifyMOIDeletion:

OpenAPI/provMnS.yaml:116:         $ref: '#/components/schemas/notifyMOIDeletion-NotifType'

OpenAPI/provMnS.yaml:129:       notifyMOIAttributeValueChange:

OpenAPI/provMnS.yaml:137:         $ref: '#/components/schemas/notifyMOIAttributeValueChange-NotifType'

OpenAPI/provMnS.yaml:150:       notifyMOIChanges:

OpenAPI/provMnS.yaml:158:         $ref: '#/components/schemas/notifyMOIChanges-NotifType'

OpenAPI/provMnS.yaml:365:        - notifyMOICreation

OpenAPI/provMnS.yaml:366:        - notifyMOIDeletion

OpenAPI/provMnS.yaml:367:        - notifyMOIAttributeValueChange

OpenAPI/provMnS.yaml:513:    notifyMOICreation-NotifType:

OpenAPI/provMnS.yaml:530:    notifyMOIDeletion-NotifType:

OpenAPI/provMnS.yaml:546:    notifyMOIAttributeValueChange-NotifType:

OpenAPI/provMnS.yaml:569:    notifyMOIChanges-NotifType:

OpenAPI/genericNrm.yaml:297:        - notifyMOICreation

OpenAPI/genericNrm.yaml:298:        - notifyMOIDeletion

OpenAPI/genericNrm.yaml:299:        - notifyMOIAttributeValueChanges

Please see further details:

• https://forge.3gpp.org/rep/sa5/MnS/blob/SA88-Rel16/OpenAPI/genericNrm.yaml
• https://forge.3gpp.org/rep/sa5/MnS/blob/SA88-Rel16/OpenAPI/provMnS.yaml

END