2024-07-24 RSAC Meeting notes

05min

admin

@Rittwik Jana 

• Next meetings

  • Tue 2024-07-30 9pm EDT by @Rittwik Jana 

  • Wed  2024-08-07 8am EDT by @Martin Skorupski 

  • Tue 2024-08-13 9pm EDT by @Rittwik Jana 

  • Wed  2024-08-21 8am EDT by @Martin Skorupski

05min

O-RAN F2F demo

@Rittwik Jana 

Request to all PTLs

• Please think about what are you going to demonstrate at the O-RAN F2F in Montreal Oct28 to Nov01.

• We would like to understand how to structure the demo sessions.

• Format does not matter much - content matters - live demo and/or recorded, with and with out slide set - you decide

• Message to O-RAN: O-RAN-SC is alive and needs further support

O-DU and OAI integration

• description by email

Non-Rt-RIC - with AI/ML

• candidate - details will be discussed

SMO - Tacker

• EtSI profile - fault management, performance management is target

SIM @Alex Stancu 

• Hierarchical OAM functions Use Case

OAM @Martin Skorupski 

• ...

• Martin plans to be in Montreal, but it is not finally confirmed.

20min

Blockers - general discussion:

@Rittwik Jana 

• SMO @Seshu Kumar Mudiganti 

  • Feature release is completed - is there a link? AI Martin 

10min

Software release procedure

@Martin Skorupski 

The importance of developer guides and software release processes:

1. Clear structure process will reduce efforts in the code contribution process and will leads to world wide know and understood processes. This way, it is also easier to get contributions from developers any developer anywhere.

2. Well defined process and pipelines will avoid adding problematic software artifacts into releases.

On the O-RAN-SC wiki we have some Developer guides, which the different teams should follow:

• https://lf-o-ran-sc.atlassian.net/wiki/display/ORAN/Project+Developer+Wiki

LF itself has nice pages and training:

• https://training.linuxfoundation.org/training/beginners-guide-open-source-software-development/

• https://www.linuxfoundation.org/resources/open-source-guides

• https://training.linuxfoundation.org/training/creating-effective-documentation-for-developers-lfc112/

Please have a look - and correct or make us aware of misleading or outdated statements. 

updates for new release should follow concepts of previous releases or should changes and concepts should be better documented

upgrade procedures could help

05min

gerrit clean up

@Martin Skorupski

https://gerrit.o-ran-sc.org/r/q/status:open,25

10min

OSC integration use case

@all

target: drive collaboration

integration use case across o-ran-sc projects

• have a look at the MVP use cases - as inspiration

• MVP might be not the target

int - focus on pairwise testing to focus on feature implementation by the projects 

00min

Q/A

@all

• if any

End of the meeting