You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 3
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-06-30: John Keeney 2021-07-07: Martin Skorupski 2021-07-14: John Keeney 2021-06-21: Martin Skorupski |
00:06 | Requirement | | |
00:05 | O-RAN-SC | O-RAN-SC PTLs | Status reports: - 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 | | 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
|
00:23 | |
| |
|
|
|
|
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.
- Paweł 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