2025-05-28 WG2 O-RAN Agenda & Minutes
Attendees
@Stefan Bjurström @Sagar Arora @balaji varadaraju@Dibas Das
Agenda
Previous Meeting Notes Approval
Meeting Next Week Cancelled
Sylva Alignment Meeting
O-Cloud Registration - Vishwanath (Lead)
Minutes
Previous Meeting Notes Approval
Approved
Meeting Next Week Cancelled
No meeting next week June 4th due to O-RAN F2F
Sylva Alignment Meeting
No meeting May 12 during SIG Architecture meeting, still needs scheduling
Update 28/5: Bala and Sagar will follow this up with TSC chair, Sana
O-Cloud Registration
Discussion points
If O2IMS operator is installed, can we try adding support in IMS to invoke the FOCOM endpoint for registering the IMS?
We could either use the O2ims specified Notification.Callback URI and extend it with a credentials parameter or create our own API for O-Cloud registration.
If a cluster has been created using O2IMS operator, could FOCOM query for list of clusters created? Which IMS API should be implemented?
The DMS object is part of the O2ims stage 3 specification. But the NodeCluster is only in the stage 2 Information Model spec right now.
We can use a pre-standard implementation to store a NodeCluster list for Nephio R5. E.g. a CRD for an O-Cloud NodeCluster.
We should also align to the official O-RAN API in Nephio. The approach for this could be that Nephio accepts the standard O2ims REST API and convert it to the currently used ProvisioningRequest CR. Correspondingly the NodeCluster could be represented internally as a CR and then exposed towards FOCOM based on the O2ims REST API.
We have not planned to do any of this in Nephio R5, will need to be planned for R6.
Would returning the list of blueprint packages registered with PORCH be considered returning O-Cloud templates?
The O-Cloud template is currently only modelled in stage 2 (information model) in O-RAN, not in the stage 3 spec in O-RAN. Could be a candidate for Nephio R6 in December.
See discussion board for updates -
ORAN O-Cloud Registration story · nephio-project nephio · Discussion #899
Proposal for next step: Update the O-Cloud registration user story with the implementation details based on our discussion above.
User Story - O-Cloud Registration (O-Cloud Registration document in Nephio)