...
- Deploy tacker on the top of the O-Cloud – 2023.
- Get the new resource (sub-cloud / edge) details. - queries the info from the O2 IMS deployment Mgr. – 2023 - Shashi - Done
- Gather all the DMS instances on the subclouds that are created from the IMS - Get query -2023 – Shashi - Done
- FOCOM to the OCloud Deploy Mgr - Shahsi
FM data of APP and connectivity to Tacker notification? - Toshi san to update us by Monday 27th Nov 2023.
Integrate the APp data with the Callback function - Shashi
VNF DMS API of WG6 - Provided by Kuno San
https://docs.openstack.org/api-ref/nfv-orchestration/v2/vnffm.html
https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/04.03.01_60/gs_NFV-SOL003v040301p.pdf
View file | ||||
---|---|---|---|---|
|
View file | ||||
---|---|---|---|---|
|
Nephio SIG-1 - WG2 integration with OSC:
Nephio Deck (5,6)
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?
Previous Agenda
23-11-27
- O-RAN SMO enhancements - Aarna Networks (Bhanu and Sandeep)
View file name SMO_Upstream_Aarna.xlsx height 250 Problem Statement: While trying to remove the device, the callhome device doesn’t get removed and the mount point that we’re trying to remove is not found.
Impact: Customer will not be able to remove the call home device from SMO
Workaround: None. In the worst case scenario, restarting of the call home device or disconnecting the netconf client will work which may not be a viable option for the customer
RCA: Document Attached
Community JIRA: https://jira.opendaylight.org/browse/NETCONF-989
Community Forum: Attached the image (in ONAP CCSDK)- Continuation to the previous discussion on ONAP SO vs SMO
- Planning to have a discussion on the Nephio R2 F2F meeting - to talk on how these communities can collaborate in the long run
- Operator based, ASD, integration points across these communities and see how can we leverage the functionalities.
- Timo, Seshu and Byung to participate and present the ideas around the topic.
- ONAP E2E orch, Nephio domain and ORAN for the RAN specific workloads as a starting point.
- (Byung) Sana discussed on WG1 Nephio on how the NFVO and other components would interact.
...