Page History

O1-VES collection (@33:30 in recording)
- PM Mapper - for PM Bulk
  - Stanislav Marszalek Stanislav Marszalek Slides:
    - View file
      name 20210728 - Stanislav Marszalek - PM Mapper - output.pptx
      height 150
  - O1 is just via ves:fileReady → FTPes
  - issues in PM-Mapper should be handle via Jira ans slack
    - https://lists.onap.org/g/onap-discuss/message/23433
    - DCAEGEN2-2874 PM Mapper output - sMeasTypesList
      Jira
      server ONAP Jira
      columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverId 425b2b0a-557c-3c0c-b515-579789cceedb
      key DCAEGEN2-2874
    - DCAEGEN2-2873 PM Mapper output - granularityPeriod issue
      Jira
      server ONAP Jira
      columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverId 425b2b0a-557c-3c0c-b515-579789cceedb
      key DCAEGEN2-2873
  - issues in VES spec are more problematic, as O-RAN Alliance is using the domain "stndDefined"

INFO: PM Streaming: ASN.1 via WebSocket according to O-RAN Spec - O-RAN Operations and Maintenance Interface 4.0 - November 2020

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

00:01

O-RAN-SC

O-RAN-SC PTLs

O-RAN-SC ToC

new o-ran license "SSCL" - not sure how to use (yet) - extra repos for such license.
guidance requested
PressRelease for D-Release ongoing...
repo clean up

Non-RT-RIC: John Keeney
- maintenance release progress
- plans for e-release → support of rApp → presentation in about 2weeks
SIM: Alex Stancu
OAM: Martin Skorupski
O-DU:HariomGupta(HCL)

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)

00:40

SMO deployment options

Christophe Closset

SMO deployment options

no tested helm for OAM in O-RAN-SC D-Release - idea update the one from C-release
for Non-RT-RIC a new helm is available - still some updates to be done
Please see presentation within
Jira
server ONAP Jira
serverId 425b2b0a-557c-3c0c-b515-579789cceedb
key REQ-887

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

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://

00:37

E-Release use cases

Very early discussions!

Disaggregated VES discussion to see if there is any feedback from the group
- Discussed at RSAC/SMO call last week:
  - Slides see: https://wiki.o-ran-sc.org/download/attachments/1179971/Disaggregated%20VES%20-%20OSC%20Release%20E.pptx?api=v2
  - Recording: https://zoom.us/rec/share/ENNFTIViSpkG6rBCzF-myIbR2i9WPzje9v7dBL0fGAI2ZM0uveyHqqBP0SkLGa3s.GQS0sL3rPgPErPsc

We could discuss the O-DU-high / O1 closed loop use case from RSAC?
called also : "Slice Resource Quota Provisioning and Assurance"
.

new version: https://wiki.o-ran-sc.org/display/RSAC/E+release+planning

00:40

SMO deployment options

Christophe Closset

SMO deployment options

no tested helm for OAM in O-RAN-SC D-Release - idea update the one from C-release
for Non-RT-RIC a new helm is available - still some updates to be done
Please see presentation within
Jira
server ONAP Jira
serverId 425b2b0a-557c-3c0c-b515-579789cceedb
key REQ-887

Meeting? on Friday 6/25

https://

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

lists

- - wiki.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:2021-06-23 Meeting notes - Joint

- - 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:

- Attempting to replicate functionality in OSC OAM/NONRTRIC/SIM

SCRUM meeting >

- 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: 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 ...
- 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:

@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 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.

VES - CM-Notify

Pawel Slowikowski

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 details2021-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.

Q/A

Info:

Jira

server	ONAP Jira
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	CCSDK-3422

Please see comments:

Caused by implementing ~~CCSDK-3387~~
Use fix, provided via https://jira.onap.org/browse/SDNC-1587 to do a local compile.

Q/A

00:21

<End>

END

00:00

Use Case

@all

OSC Proposed e2e integration use case: O-RU FH connection recovery

REF/Background:
- (OAM) Closed loop use case
- (RSAC) Meeting 14 Jan:
  - Slides: https://wiki.o-ran-sc.org/download/attachments/1179971/RU_failure_recovery_use_case.pptx?version=1&modificationDate=1610637325824&api=v2
  - Recording: https://zoom.us/rec/share/mKYOGkB3mgpvIo2Hx1eY5Oifyw9qV9NQd7NiEj-FxQKP0kUpWOc7yvMO_LLPhA_M.lmx2LCh7-QwDHAFi
Martin Skorupski provided intro
- Alarm when fronthaul connection dies (O-DU - O-RU) (VES to SMO)
John Keeney If there is a failure both O-DU & O-RU will try reconnect anyway - without this loop? Martin Skorupski Yes.
@? How does SMO connect to O-RU?
- Martin Skorupski This is a mix of different deployment options (hierarchical vs hybrid, O1 vs M-Plane). Main issue is agreeing models & terminology.
John Keeney Seems this use case is not real-world useful, especially since recovery will happen automatically anyway, & mix of standards ...
Martin Skorupski John Keeney Using this use case as longer term motivator for SMO/NONRTRIC/rApp development - independent of usecase
Topology ??:
- May need a topology service for this use case - John Keeney Will use a simple file/hardcoded for initial versions of this use case.
- Pawel Pawlak Andy Mayer Topology in A&AI, CPS ? John Keeney No - not initially. Plan to keep it simple for this release.

Topology ??: (contd)
- John Keeney Lots of options for how this should be done properly in ONAP.
- Swaminathan Seetharaman ONAP usecases already have some plans for this e.g. slicing, oof, etc
- Andy Mayer A model should be agreed in ONAP. Lots of previous discussions in ONAP - e.g. what goes in A&AI and CPS ... but that was a while ago.
- Martin Skorupski SDNR has some topology model too - not standards based.
- @Sven John Keeney Martin Skorupski Lots of issues with different topology models ... and most existing hierarchical models break down in a 5G/CloudRan environment
- Lots of work ... Andy Mayer Martin Skorupski Can create a JIRA in ONAP MODCOM ...
- ... but will keep it simple here for this use case.
@? Will other O1 usecases be effected? Martin Skorupski i No. O1 functions continue as before.
Martin Skorupski Please add feedback if any

Action items

Space shortcuts

Page tree

Versions Compared

Old Version 2

New Version Current

Key

Attendees

See also

Goals

Recording

Discussion items

OSC Proposed e2e integration use case: O-RU FH connection recovery

Action items