You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
Version 1
Next »
Please add/remove yourself. Thanks!
See also
Goals
- share information between
- O-RAN-SC Non-RT-RIC
- O-RAN-SC OAM
- O-RAN-SC O-DU
- ONAP CCSDK/SDNC/SDN-R
- LFN
Recording
Discussion items
Time | Item | Who | Notes |
---|
00:00 | Admin | | Next meetings: 2021-07-21: Martin Skorupski 2021-07-28: John Keeney 2021-08-04: Martin Skorupski 2021-07-11: John Keeney |
00:05 | O-RAN-SC | O-RAN-SC PTLs | O-RAN-SC ToC Status reports: |
00:30 | SMO deployment options | | 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
REQ-887
-
Getting issue details...
STATUS
Meeting? on Friday 6/25 https://lists.onap.org/g/onap-meetings/viewevent?repeatid=37969&eventid=1192141&calstart=2021-06-25 - 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
- @Christophe : Meeting upcoming
- Every Friday:
- 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
- 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
- @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? 2021-07-07: way forward 2021-07-14: |
| Q/A |
|
|
00:16 | |
| |
END
|
|
|
|
00:00 | Use Case | | OSC Proposed e2e integration use case: O-RU FH connection recovery- REF/Background:
- 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.
<bridge dropped recording stopped at this point. Most participants reconnected once bridge started again> - 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