Agenda:

Update: 27th  March

Risk :

No common lab found to test the components ( FOCOM, NFO (ETSi and K8s), DMS, OAI and Nephio). 

No complete setup is still available.

Taiwan Lab- 

One O-Cloud server is being helped from Taiwan lab - Bimo would to provide the details.

Got  a machine from Taiwan lab, thnks to Bimo, would need another server to test the FOCOM and NFO.

Need another server to deploy the SMO components, can get the lab for a month or 2 - BIMO will help us on this.

OAI lab -  

Procurement of the servers is in progress. Sagar - would be updating us on this.

2 servers (Intel 5th gen) are obtained and installation would begin from next week. 

West and East coast Labs 

Challenging to get the labs at the moment - James 

no update

Powder servers would be a temp soln, weather it would be applicable to this integration - Need to investigate this further - Sagar

India Lab

Capgemini - Vishal would get back on this. 

Yet to complete the installation, the public IP config has some issues and being sorted out.

Japan Lab

OTIC - Toshi would check this part and update.

No update yet, Kuno san would check with the the OTIC lab on the servers avaialability.

Cosmos Lab

The lab is still not available - Martin

Contingency plan:

We would use the Taiwan Lab for the testing using the VM for SMO as a starting point.

This would be temp soln and would need to be mitigated asap.

Mitigation Plan:

To have a dedicated lab to test the E2E scenario, to help OAI with the needful approvals to accelerate the lab setup.

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:

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

ONAP SO vs SMO sync - Byung and Seshu

30th Aug 2023

Create Stories under the Epic for the I release and follow up.

This is the current target for the I release

• • 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.
  • O2 should have some way in IMS to register that would help us to make the connect to the DMS, DMS would be exposed and consumed but we would need to have the connect to have the E2E registration between the IMS to the DMS flow. (David)
  • This would also include the parts of the inventory that would need to be on the FoCOM part that needs to be exposed and consumed by the DMS and deploy  the workloads (Seshu and David)
  • Missing part is not described in ORAN yet but in ONAP with the interactions with the inventory function (Shankar).
  • E2E flow would be to have the FoCOM and NFO to have the interactions and have the handsoff with the change in the inventory record, the nature of the de-coupled SMO would not have the explicit event to DMS.
  • A messaging bus with a pub-sub would be ideal to have to this transition notified.

--------

SMO to OAM

• • Toshi CRs for the possible flows on the SMO in the WG1 - (need to reexamine and start it to see how would it help us to have the above points addressed).
  • Try to influence the WG1 with a sample implementation. 
  • Restore the older flows of Toshi and put them up for the upcoming meetings. (David).

2nd Aug 2023

Review the ETSi profile DMS slide deck through Tacker flows and prep for RSAC meeting.

Find the integration points,

correct the ETSi sol definitions around the APIs, 

Architecture diagram to be reviewed from the E2E flow.

Test cases to be reviewed if and when they are ready.

Energy Saving 
Rittwiki

4 capacity cells and coverage cell in center, generate the PM metrics (Like throughput) and use it for AI ML mode testing.

The ask is was to check if we have a simulator that can generate such a data can be used dynamic based on the time of the day.

Once they are generated they can be used by the AI ML project and then the rApp projects to simulate the required data and validate the flows.

Step 1: Detect / predict, through AI ML body.

Step 2 : once detected we should be able to perform action through the rApp. handle the users and switch off the cell.

Alex confirms we don't have a ready to use simulator yet but needs to check if that can be made available. 

This can further be checked in ToC meeting this week.

30 Aug 2023:

Data set from Tim would be a starter.

Viavi volunteered to help and test it 

Train a model and Bimo (Taiwan) would help

Connect Udi with Ritwik for Energy efficiency Plugfest data. - Seshu

• The placement of the Tacker code needs to be clarified - Toshiaki.
• Update the flow diagram for the homing, inventory and deployment of the NFs using tacker - Toshiaki
• Test case to be used - co-ordinate with Integration team -  CSAR package from the prev package - Toshiaki
  • Step 1 : A simple app that can be considered as a low lying fruit to validate the flow
  • Step 2:
  • Possibilities are VNFM  Radisys OCU / OAI-OCU for the E2E flow testing once they are ready
  • NRT RiC that could be deployed on oCloud.
• The FM data on O2 is available in Nov 2022, on O2 IMS.
  • @David Kinsey
  • This need to be validated and on the IMS part and DMS needs to be clarification.
  • ORAN-SC-INF has already validated the FM data part in their release package.
  • PM would be available by March 2024
  • @Yuya Kuno : Currently O-RAN WG6 is pending on FM/PM of O2dms, but O2dms of NFV-Profile started to develop FM/PM based on SOL002/SOL003 by Nov train.

2023-08-23 Meeting notes:

Recording