Versions Compared

Version Old Version 4 New Version Current
Changes made by

Seshu Kumar Mudiganti

Seshu Kumar Mudiganti

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • 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
    namevideo1481058530.mp4
    height150
    View file
    nameNF Orchestration Using SMO (Design details).pdf
    height150
    Image Added

2024-01-31:

J Release targets:

ETSI DMS profile enhancement.

https://wiki.o-ran-sc.org/download/attachments/35881444/Tacker%20J-Release_for%20SMO_Jan_rev1.pptx?api=v2

K8s profile Integration to the SMO code - Draft.

...

SMO (FOCOM/NFO) functionality:

    1. 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? 
    2. Would the SMO be able to deploy a packaged O-RAN using the K8s DMS profile? 
    3. 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)
  2. O-RAN NF
    1. 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) 
    2. 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?

...

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.

...