Page Comparison

Agenda:

Toshi San would be the point of contact for us to handle the Tacker related issues under SMO.

F2F meeting in Oct in Montreal

...

1. TE&IV demo (may be through simulators) - John KDemo on Fault Mgmt through Tacker for DMS ETSi profile. - Kuno san
   1. SMO O2 (FOCOM and NFO (K8s)) demo of the IMS and DMS (as a possibility) - Seshu
   2. Nephio integration with the OSC-SMO (as a stretch and possible idea for the demo) - Seshu
   3. 1. Standalone demo of the TE&IV FW code with the sample schema and models - 28th August 
         1. story around the RAN CNFs and their relations across the deployments
         2. RAN functions (across cloudsite) deployed as CNFs and query their Topography
         3. rApps and Non-RT RiC integration capabilities across the SMO and RIC
      2. Usecase defined models to be incorporated and showcase the Capabilities once the sample data are available (Stretch)
         1. Topo info is loaded we can showcase of the CNF migration across the subclouds (also at the Geo-Distributed arena)
         2. sync DMS data between Tacker and datastore model (draft version) and show the effects of that on the CNFs - (long run goal)
   4. SMO O2 (FOCOM and NFO (K8s)) demo of the IMS and DMS (as a possibility) - Seshu
   5. Nephio integration with the OSC-SMO (as a stretch and possible idea for the demo) - Seshu
   6. Demo on Tacker for DMS ETSi profile. - Kuno san - Video 14th August
      1. FM:
         1. Fault mgmt we can have the demo - we will focus on the faults of the Workload and listing them
         2. To have the Tacker being able to handle (core-relate, handle like in control) the faults and manage it (Stretch goal).
      2. PM:
         1. J release code would be used to demo based on Tacker
         2. Client side impl would be required and can be targeted by the demo time.
   7. Secure communication between the modules - this is in general between the OSC components. (Stretch Goal across the ORAN-SC modules)
      1. Dmaap - Kafka messaging
      2. Strimzi based comm as an extension to the above one.
      3. this needs to be implemented across the OSC components (like pub-sub)

   ...