...
- ETSi DMS (through Tacker) - Toshi
- OAI oDU to be instantiation through the ETSi Profile (Tacker)
- Stretch : FM Data from the OAI oDU (TB Checked on API and workload) if can be generated and captured by the Tacker (This is in-line to the Plugfest NA (Dec -2023) usecase).
- Action 1 : Seshu to check with OAI team on the possibilities. ODU PTL (Ankit) to be checked for the example implemented in the OSC.
- 2 : Toshi To discuss the E2E scope of this functionality. (Involve OAM)
- PM Data would be a future scope item.
- 3GPP File based are already supported by RIC- John
- Stream based is open - John.
- FOCOM - Seshu
- NFO K8s Profile - Seshu
- Recording:
View file name video1481058530.mp4 height 150 View file name NF Orchestration Using SMO (Design details).pdf height 150 
2024-01-31:
J Release targets:
ETSI DMS profile enhancement.
K8s profile Integration to the SMO code - Draft.
...
SMO (FOCOM/NFO) functionality:
- Would the SMO be able to have the ability to define an O-Cloud and then support the registration of the O-Cloud via the IMS interface?
- Would the SMO be able to deploy a packaged O-RAN using the K8s DMS profile?
- If so then we can do the use cases (bolded) in slide 5, 6. The others would be incorporated once the SMO supports those features (e.g., inventory, O-Cloud retrieval)
- O-RAN NF
- Can we at least 1 O-RAN NF (say O-CU CP) and deploy that package via the SMO/NFO? (This would mean the package would have to be in the format the SMO could understand)
- Can use O1 to change the configuration of an O-RAN NF (e.g., DU) – what, if anything, do we want to show regarding the O1 interface? Sagar said: DU we can configure via O1 and get the heartbeat. Can the SMO support this type of change?
...