Running Meeting notes

2025-12-03

Agenda

• Discuss on the ORAN Plugfest

  • Demo status update - Kuno

    • 12.04 is the demo date in the plugfest and we are ready for the demo.

    • https://o-ranalliance.webex.com/meet/PlugFest

  • Demo video - Kuno

    • Link to updated after the plugfest @Yuya KUNO .

  • Feedback for Devtron for the help in the demo of ORAN-SC F2F Oct meeting and ORAN Plugfest:

    • @Yuya KUNO @Martin Skorupski @Toshiaki Takahashi @Seshu Kumar Mudiganti

    •  

• ORAN-SC M release closure

  • SMO page to be with the details.

  • M-ReleasePreview

  • Code and Docs to be updated.

• ORAN-SC N release requirement gathering.

  • Discussion are through in ORAN-SC RSAC for Deployment of k8s and Nephio enhanced to support the O2 interactions in SMO.

    • @Martin Skorupski to help us update on this as it unwinds..

  • Tacker team to provide ETSi Profile to bring flow Auto-homing and Auto-healing

    • Highlight the scope of the work and Link to Flow to be updated by @Anurag Mishra

  • Candidate for the SMO - FOCOM and NFO:

    • Nephio integration we need the support from community.

      • Reach out to Bimo to get the intern help - @Toshiaki Takahashi

    • Potentially Devtron as the candidate for the flow as we did in the last release.

      • Devtron to be introduced in RSAC team for better visibility - @Toshiaki Takahashi

      • Action to put it on Agenda for RSAC meeting - @Martin Skorupski @Abhibhaw

• ToC meeting Update - @Martin Skorupski

  • Discussions on for the decision on ORAN-SC to move from LF to LFN

  • SMO to leverage the ONAP-SO / OAM / Policy / SDN-C (SDN-R)

• @Ashutosh Mishra raised a point of ACC-100 in the Win-Lab:

  • Lab to migrate from Windriver internal to Winlab and need ACC 100 for the Homing usecase realization.

  • In the Win-Lab Intel team suggested to use processers (Sapphire Rapids or Granite Rapids) to be compatible for ACC-100/200 as it already provides. @Martin Skorupski to check with @Ivan Seskar

2025-05-21

Introduction to Devtron - Abhinav

Open

Discussion on the Oct F2F event strategy - Kuno San

2025-04-23

Open

2025-03-12 Meeting notes

1. ORAN F2F meeting details:

   1. 2025-02 O-RAN F2F Paris - Events - Confluence/Wiki

2. Tacker team proposal for the L release - Toshi san 15 mins

   1. https://lf-o-ran-sc.atlassian.net/wiki/download/attachments/13570027/Tacker%20L-Release_for%20SMO_Jan_rev3.pptx?api=v2

3. Open MSA introduction session in the next SMO session - 25 mins (continuation from UBiqube).

Open

Prev Agenda:

1. https://lf-o-ran-sc.atlassian.net/wiki/download/attachments/13570027/Tacker%20L-Release_for%20SMO_Jan_rev1.pptx?api=v2 - Toshi san

   1. We will revisit the Tacker work load for the K release and evaluate the tasks committed.

2. Open MSA as a NFO has been brought to the notice of the SMO by Tacker team https://github.com/openmsa 

   1. We need more clarifications on this item - Kuno San to get back with the details.

   2. Some of the key aspects to check would be

      1. Licensing of the Open MSA (GNU license...)

      2. Providers and maintainers of the code base - (UBiqube, Fujitsu... )

      3. Background of the arch, design and integration points with the SMO

      4. NFO should ideally support both K8s and ETSi DMS, this should also be checked in detail

      5. How the existing code can integrate with this tool needs to be clarified

      6. K release would be too short to include it in the main stream, would recommend to clarify these details and then would collectively take the decision

      7. We would look into the details and take further decisions, this could take multiple  iterations as and when needed.

      8. Would like to propose the collective findings to the RSAC and ToC for the approval before we commit it as part of the release.

3. Open MSA introduction session in the next SMO session - 20 mins (Herve Guesdon from UBiqube).

4. NFO intro for the demo provided as part of the Montreal F2F - (Vamsi / Vishal) - Open Item

5. T&IV - K release scope - John K

   1. Model are being refined for the ORAN integration,

   2. Entity groups are being evaluated and worked upon.

   3. WG10 of ORAN spec are being worked upon and recommendations would be provided as we find the updates

   4. N/w Topo generator is being used to fill the topo view and the integrations adapters are being worked upon. - Martin S

   5. Gather logical view from the ETSi profile of the deployed nodes through tacker is being requested. Toshi san

6. Usecase defined models to be incorporated and showcase the Capabilities once the sample data are available (Stretch)

   1.  

      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)

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)

   4. SMO (O2) DB

8. K-Release details

   1. K Release#ServiceManagementandOrchestrationLayer(SMO)

Recording:

Open

Completed tasks

→ F2F meeting in Oct in Montreal - 28th Oct - 31st Oct.

2024-10 O-RAN F2F Montreal

Target and Showcase the demos for the 

1. Topology Exposure & Inventory (TEIV)

   1. TE&IV demo (may be through simulators) - John K

   2. https://lf-o-ran-sc.atlassian.net/wiki/download/attachments/13568120/20241030-OSC-SMO-TEIV-Intro%2BDemo-MontrealF2F2024-JohnKeeney.pdf?version=1&modificationDate=1730715717979&cacheVersion=1&api=v2

2. SMO O2 (FOCOM and NFO (K8s)) demo of the IMS and DMS (as a possibility) - Shashi and Vamshi

   1. https://drive.google.com/drive/folders/1kWhqy219L2kebXfBf2Q9lUyY2pkXDiyp 

3. Nephio integration with the OSC-SMO (as a stretch and possible idea for the demo) - Vamshi

   1. NFO demo through SMO

   2. https://drive.google.com/drive/folders/1kWhqy219L2kebXfBf2Q9lUyY2pkXDiyp 

4. Demo on Tacker for DMS ETSi profile. - Thoshi and Tacker Team
   
   

   1. FM and PM data 

   2. https://drive.google.com/drive/folders/1H8eISd6CFeI72fl1AsntD3DuTPaufDQW

Tag meeting to UTC or Current time:

Future tasks

Open

5th June

TE&IV and SMO discussion continuation

1. Seed code is checked-in and review

   1. it seems ok to have it in? - Seshu

      1. https://gerrit.o-ran-sc.org/r/c/smo/o2/+/12927 

      2. The comment was the ease of understanding would be better to have the doc for larger understanding

      3. Please provide overview intro for the larger audience understanding

      4. Slides: 
         

   2. Would discuss the details - John

      1. TEIV Seed code: 

         1. There you will see a root maven pom.xml file to build the functions.
            I’ve created a JIRA ticket at https://jira.o-ran-sc.org/browse/SMO-147 

      2. The early documentation is in progress

      3. further would be prepared in parallel that includes overview and usage details

2. Discussion on the Perf data for Tacker - Toshi

   1. we will use the OAI DU (CU) for onboarding in the next release through Tacker.

   2. O2 perf data (ETSi) examination would be next release candidate

   3. Need help in improving the documentation in this release.

8th May:

ONES Session Udpate

https://gerrit.o-ran-sc.org/r/c/smo/o2/+/12850 - NFO commit patch for SMO

SMO FOCOM code checkin - in progress

TE&IV and SMO discussion continuation

1. Seed code is expected to be available by this week.

2. Once we have the seed code is available, we will have sessions planned for code walk through by experts.

3. Tonie and John would help us with the deep dive on the specific topics possible starting 3rd week of May 2024

24th April:

Ericsson proposal to contribute some Topology & Inventory functions in O-RAN SC - @Tony Finnerty @John Keeney (Ericsson EST) 

• Initial focus: Inventory & topology store, query service (& API), and initial models. Goal to support & align with WG10.

• Looking for the Community Engagement to support this functions

• Slides:
  

• Next step: secure somewhere to store proposed seed code for review, and if accepted possible first release in June (Rel J)

o-ran-sc-SMO work with Nephio

Open

Open

Update: 27th  March

Risk :

Taiwan Lab- 

OAI lab -  

West and East coast Labs 

India Lab

Japan Lab

Cosmos Lab

Contingency plan:

Mitigation Plan:

NFO (DMS K8s) : 

                  the coding of the NFO K8s profile to integrate with Helm client, is completed and testing is in progress

                    Helm repo as a repo is awaited for the OAI helm charts.

                   The future step is to have the DMS K8s profile APIs to be realized through the NFO SBI.

NFO (DMS ETSi through Tacker) :

                Tacker integration the Ocloud is targeting the FM/PM usecase has started.

                Next work is to complete the sequencing and have the FM/PM usecase implemented.

                FM data was demoed using the simulators in the plugfest of Nov 2023. 

                PM data needs a deeped digging on how to be demoed.

FOCOM:

              The O-Cloud operator that is developed as a pet project is being refined.

              We are currently adapting to the Nephio operator way, we are bridging the operator to work for both OSC and Nephio.

              Once the translating is complete we would need an env to test it E2E with a new cluster on the OSC-INF.

Nephio SIG-2 Automation:

               We have yet to present it in a future meeting, where we need to present the way Nephio and OSC.

Futuristic Functions in SMO:

Inventory

            Currently we are dependent on the IMS data base for all the related info of the clusters.  

            This needs to be corrected and have the updates directly in the SMO Inventory (closer to IMS).

             IMS should update this inventory on any change made to the underlying O-cloud.

             Esp NFO currently fetches the DMS id from IMS database.

            The current inventory simulator in the OAM component is more of a reference than a realistic inventory.

            AAI was one of the candidates, but is found too heavy for the RAN based operations.

SO (as an E2E orchestration piece)

         This is being discussed in the ORAN WG1 and would be integrating with both FOCOM and NFO.

         SBI of SO would integrate with the current FOCOM and NFO.

         Homing and placement decisions would be part of the SO and would drill down to the NFO for the actual work delegation.

J release:

Updates from Nephio, OAI integration work.

Create the Epics and stories for the

• 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: NF Orchestration Using SMO (Design details).pdf

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.

2024-01-10:

I release status.

OAI integration

J release proposal.

• discuss 

2023-12-20:

ORAN NA Plugfest update

• https://oranalliance.atlassian.net/wiki/spaces/PLUG/pages/2907668584/O-RAN+Internal+presentations+-+PF+Fall+2023

I release management:

• I want to merge the following patches

• https://gerrit.o-ran-sc.org/r/c/smo/o2/+/12180

• https://gerrit.o-ran-sc.org/r/c/smo/o2/+/12169

• https://gerrit.o-ran-sc.org/r/c/smo/o2/+/11738

• https://gerrit.o-ran-sc.org/r/c/smo/o2/+/11886

• https://gerrit.o-ran-sc.org/r/c/smo/o2/+/11280

• Then, I want to update release note based on the above.

• https://gerrit.o-ran-sc.org/r/c/smo/o2/+/12400

2023-11-22:

ORAN NA Plugfest details

Pre-requisite:

• Setup the Lab

• O-Cloud with the edge is already brought up. –(showcased in 2022)

• Tacker is deployed on the O-Cloud- Showcased in H release.

2023 is focus is on the ETSi profile

• 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://oranalliance.atlassian.net/wiki/download/attachments/2210595103/O-RAN.WG6.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R003-v05.00.02.docx?api=v2

https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/04.03.01_60/gs_NFV-SOL003v040301p.pdf

Nephio SIG-1 - WG2 integration with OSC:

Nephio Deck  (5,6)

SMO (FOCOM/NFO) functionality:

1.  

   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?

Previous Agenda

23-11-27

1. O-RAN SMO enhancements - Aarna Networks (Bhanu and Sandeep)

2. 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)

3. Continuation to the previous discussion on ONAP SO vs SMO

   1. Planning to have a discussion on the Nephio R2 F2F meeting - to talk on how these communities can collaborate in the long run

   2. Operator based, ASD, integration points across these communities and see how can we leverage the functionalities.

   3. Timo, Seshu and Byung to participate and present the ideas around the topic.

   4. ONAP E2E orch, Nephio domain and ORAN for the RAN specific workloads as a starting point.

   5. (Byung) Sana discussed on WG1 Nephio on how the NFVO and other components would interact.

Prev Discussion items - 

2023-09-13

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.

30th Aug 2023

•  

  • Tacker would be integrated with Inf project and DMS interfaces would be tested .

  • Tacker should continue the H release effort and then take it forward

  • Who would start the flow (David)

    • We would start with the interfaces with the inf (Seshu)

    • This is ok, but need to also make sure we would need the other components in the SMO in the long run. need to check when and how long would it take to reach it.