Page History

Non-RT-RIC: John Keeney
- releasing the D-Release - final regression tests
- deployment in O-RAN-SC Lab
  - link monitor app to be updated
  - feedback by Kamel Idirworks
    - Non-RT-RIC, OAM, SIM (O-RU, O-DU) 4 CPUs + 16GB → better use 8CPU and 32GB
- TOC call today
  - next week a vote for release
SIM: Alex Stancu
- as discussed already
OAM: Martin Skorupski
- Ready to create branch for D-Release
O-DU: HariomGupta(HCL)
- integration into O-DU (high) working fine
- IPv6 into fully enabled
- expectation IPv4 as NetConf end-point working - but is not - HariomGupta(HCL)sending to Martin Skorupski

00:20

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

00:48

<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.
- Paweł 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 5

New Version Current

Key

Attendees

See also

Goals

Recording

Discussion items

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

Action items