Page Comparison

ONAP Requirements subcommittee request an update on areas where ONAP and O-RAN share interest.

• What is/are the area/s of common interest?
• What is the current state of affairs?
• What are the future topics to address?
• Any issues that require more emphasis from the community, or more formal collaboration relation between the two communities is needed?Anything else you think it worthwhile to highlight.that require more emphasis from the community, or more formal collaboration relation between the two communities is needed?
• Anything else you think it worthwhile to highlight.

Updates/feedback for next Monday meeting

• SON based use case
• Slice based use case
• VES messages
• A1 Policy
• SMO Deployment
• Test environment
• Simulators
• Topology
• ...

Further discussions 

• O2 
• coordination O-RAN-SC / ONAP
• primary / secondary yang model - feedback to yang developers
• ...

Suggestion

• update LNF slides from Feb and May

Martin SkorupskiCheck with O-RAN Wg10 where the restriction to ASN.1 came from. 

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 Former user (Deleted)

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)

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

Shankar: point to a 3gpp....zip (https://www.3gpp.org/ftp/Specs/archive/28_series/28.532/28532-g81.zip → v16.8.1)

Marcin has looked into it. 

• to complete and validate the entire json - additional yamls are required.
• there are reference inside to other schemas - needs to be analyses - for validation on the ves-collector.
  • more infos next week

OOF-SON use case roadmap from last June.

Marcin was referring to slide 16 in this June 2021 LFN slide deck for the ONAP-SON use case. https://wiki.lfnetworking.org/download/attachments/56066778/LFN_June2021_ONAP_SON_Rel9_20210610_v1.pptx?version=1&modificationDate=1623339917000&api=v2

• VES message handling on SDN-R 
  • used to update CPS
  • code is in ccsdk/features - northbound (CM Notification Support in ONAP)
  • DCAE VES Collector - implementation for VES 7.2 in Honolulu  
  • TODO: add link to nexus dcae-ves-collector–image.... (???1.8.0???)
  • gerrit repo: gerrit.onap.org:29418/dcaegen2/collectors/ves

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

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 K
  • https://wikilf-onap.onapatlassian.orgnet/wiki/pages/viewpage.action?pageId=10342227215480760
    • (Updated afterward: Minutes & Recording: https://wikilf-onap.onapatlassian.orgnet/wiki/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 (Ericsson EST) 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://wikilf-onap.onapatlassian.orgnet/wiki/pages/viewpage.action?pageId=10342227215480760
    • (Updated afterward: Minutes & Recording: https://wikilf-onap.onapatlassian.orgnet/wiki/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://wikilf-onap.onapatlassian.orgnet/wiki/pages/viewpage.action?pageId=10342227215480760)

--

Are the following pages related?

• CNF/VNF deployments

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

2021-07-07:

way forward

• release helm repo by OOM should be created
  • (Added later: John Keeney (Ericsson EST) 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 ChrisC Sebastien 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 (Ericsson EST) 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.

2021-08-18:

• demo of by Samsung for CNF deployment - recording available on the Friday meeting wiki
• updates on OOM for O-RU-Sim and O-DU-Sim deployment as CNF
• work in progress

SON use case

• based on O1
• How to include A1 in the SON use case? for the Network Slicing Use Case
• Will be discussed on Use case Realization call (on Mondays)
• use case in O-RAN-SC regarding Network Slicing - similar but not in all details

END