Date
Info | ||
---|---|---|
| ||
Date: Time: 6pm PDT | 9pm EDT | 03:00 CEST +1 | 09:00 UTC 08:00 +1 Please subscribe to: https://lists.o-ran-sc.org/calendar (only there is the truth) |
Goals
- Define demo Details for O-RAN F2F in Montreal (Oct28 - Nov01)
- Define requirements for O-RAN-SC
Recordings
<to be updated after the meeting>
Table of Contents
Table of Contents
Attendees
Please add yourself, if you like.
Discussion items
Time | Item | Who | Notes | ||||
---|---|---|---|---|---|---|---|
05min | admin | Martin Skorupski |
| ||||
05min | O-RAN F2F demo |
INF
O-DU and OAI integration
Non-Rt-RIC - with AI/ML
SMO - Tacker
SIM Alex Stancu OAM Martin Skorupski
| |||||
10min | OSC integration use case | @all | Q: Would it make sense to start with "health-check" again? ... followed by "network slicing" and "Traffic steering"? Details should be documented here: Release "L" Previous meeting(s) target: drive collaboration integration use case across o-ran-sc projects
int - focus on pairwise testing to focus on feature implementation by the projects | ||||
20min | Blockers - general discussion: | (copy from previous meeting) Problems uploading / committing code to O-DU low repo
bimo fransiscus asisi Pls update here regarding xFAPI code availability and whether you are ready to test with Ashwini, Peng Lu (Deactivated) and Ankit Barve | 10min | Software release procedure | Updates for new release should follow concepts of previous releases or should changes and concepts should be better documented Upgrade procedures could help How to we make sure that information about Upgrades from one to another release are documented or known by INT team?
| ||
05min | gerrit clean up | https://gerrit.o-ran-sc.org/r/q/status:open,25 | |||||
00min | Q/A | @all |
| ||||
End of the meeting |
Action items
Decisions
- if any
References
- if any