...
- TE&IV demo (may be through simulators) - John K
- Standalone demo of the TE&IV FW code with the sample schema and models - 28th August
- story around the RAN CNFs and their relations across the deployments
- RAN functions (across cloudsite) deployed as CNFs and query their Topography
- rApps and Non-RT RiC integration capabilities across the SMO and RIC
- Usecase defined models to be incorporated and showcase the Capabilities once the sample data are available (Stretch)
- Topo info is loaded we can showcase of the CNF migration across the subclouds (also at the Geo-Distributed arena)
- sync DMS data between Tacker and datastore model (draft version) and show the effects of that on the CNFs - (long run goal)
- Standalone demo of the TE&IV FW code with the sample schema and models - 28th August
- SMO O2 (FOCOM and NFO (K8s)) demo of the IMS and DMS (as a possibility) - Seshu
- Nephio integration with the OSC-SMO (as a stretch and possible idea for the demo) - Seshu
- Demo on Tacker for DMS ETSi profile. - Kuno san - Video 14th August
- FM:
- Fault mgmt we can have the demo - we will focus on the faults of the Workload and listing them
- To have the Tacker being able to handle (core-relate, handle like in control) the faults and manage it (Stretch goal).
- PM:
- J release code would be used to demo based on Tacker
- Client side impl would be required and can be targeted by the demo time.
- FM:
- Secure communication between the modules - this is in general between the OSC components. (Stretch Goal across the ORAN-SC modules)
- Dmaap - Kafka messaging
- Strimzi based comm as an extension to the above one.
- this needs to be implemented across the OSC components (like pub-sub)
| View file | ||||
|---|---|---|---|---|
|
J-Release updates
https://gerrit.o-ran-sc.org/r/gitweb?p=smo%2Fo2.git;a=shortlog;h=refs%2Fheads%2Fj-release - Seshu
...
ETSI DMS profile enhancement.
K8s profile Integration to the SMO code - Draft.
...
Discuss on the ONAP Service orch pieces that could come handy to the SMO.
ASD, Inventory, IMS and DMS, E2E orch flow...
IMS :
once a a sub cloud is created we need that details to be avaialble to the DMS.
ETSi - profile - Tacker
The Tacker will be through helm deployment will be done on top of the OCloud,
This Tacker will then help the SMO to deploy the workloads of ETSi specific.
Tacker talks to the O-Cloud for the DMS operations - this uses the ETSi specifications and translates it internally uses the K8s APIs for the deployment.
K8s Profile - CNF orch piece of the ONAP SO
Inventory - persist the info of the clouds that are created in the Day 1.
This inventory should be the transition for all the sub-sequent operations in the SMO and further down to the other components of the ORAN(-SC).
Demo of using ONAP SO CNFM for LCM of ASD-based functions (NONRTRIC team in May 2023):
- 2023-05-17 "LCM of ASD-based CNFs using ONAP CNFM function in Standalone mode" Aravindhan Ayyanathan
- At RSAC committee Meeting (17 May 2023)
- Demonstrate ASD-based LCM for CNFs using a cut-down version of the CNFM function originally from the ONAP SO project. The function can be used in standalone mode without the need for the rest of SO, A&AI or SDC.
- See Video (HD), Video (SD) and Slides for more information
- Will add link to the ASD archives ...
Actions Items:
Stories under the Epic for the ETSi profile DMS to be created - Toshi.
...