Versions Compared

Old Version 2

changes.mady.by.user Seshu Kumar Mudiganti

Saved on

compared with

New Version Current

changes.mady.by.user Seshu Kumar Mudiganti

Saved on

Key

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

Agenda:

Running tasks  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. 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
    3. 28th Update
      1. Standalone demo is possible, with queries and basic models
      2. will be the internal review with the demo video as a iteration 1 model.
    4. 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)
  2. SMO O2 (FOCOM and NFO (K8s)) demo of the IMS and DMS (as a possibility) - Shashi
    1. 28th Update
      1. Test is in progress for FOCOM in the OAI lab,
      2. NFO is deployed
      3. E2E flow testing - TBD-Stretch for the demo video.
    2. 11th Sept
      1. We will have the mock run in the first week of Oct.
  3. Nephio integration with the OSC-SMO (as a stretch and possible idea for the demo) - Seshu
    1. 28th Update
      1. Nephio integration will start soon after the above task is completed - WIP
    2. 11th Sept
      1. We will have the mock run in the first week of Oct.
  4. Demo on Tacker for DMS ETSi profile. -  Demo ready, thanks 
    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.
      3. Review time as 11th Sept.
    3. 14th Update:

      Tacker team is working with to get an env for the demo, WindRiver is one of the possible options.

      Komiyama San is the spoc for the env from WindRiver and work is in progress.

      Need update on the previous video used in the ORAN F2F on FM in Oct 2023, and PM of J release.
      • Kuno San would share the latest videos on FM and PM recorded.
    4. 28th Update:
      • Topology is shared to Bimo by Tacker team
      • Bimo said 2 servers would be available for the demo, as soon as the OS is ready in a couple of days.
      • ORAN-SC INF  based O-Cloud to deploy the Tacker DMS and one server to deploy the SMO (other supporting tools).
        • One server for IMS and ETSi DMS
        • One server for K8s DMS 
        • One VM for the SMO
    5. 11th Sept
      1. End of the Sept 2024 we should be able to  have the demo - Toshi san, Kuno san
      2. 25th Sept 2024 would  be the internal demo day
      3. Bimo env has some connectivity issues, that Tacker team is working on at the moment.
  5. 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

View file
namevideo1088191528.mp4
height250

Prev meeting Updates:

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

J-Release updates

https://gerrit.o-ran-sc.org/r/gitweb?p=smo%2Fo2.git;a=shortlog;h=refs%2Fheads%2Fj-release - Seshu

J release build jobs update - Toshi

release notes merge - Seshu

J Release#ServiceManagementandOrchestrationLayer(SMO) - Seshu

Update with the latest info -Toshi

NFO checkin

helm application re-alignment. (I41b1fb72) · Gerrit Code Review (o-ran-sc.org) - resolved

Next step would be to have the code tested on the OAI lab - Vamshi & Shashi

TE&IV

SMO-TEIV: Add jenkins jobs (maven, docker, sonar) (Ib97f2120) · Gerrit Code Review (o-ran-sc.org) - resolved

Minor issues with the code coverage that are being tracked with the LFN team - John

we would have detailed code walk through sessions further on this in future. - John and Aravind.

DMS Fault Mgmt ETSi Profile

Would use the sample app to be provided for the current release to test the Fault mgmt,

Sample app to be uploaded - Toshi

In the future we would be using the OAI DU for the E2E testing of this feature - Seshu.

Performance Mgmt on ETSi once the standards are ready and strategy for the K release and beyond. - Kuno san

Discuss with Tata (with Intus - Taiwan University) on the ETSi - OSM - on the SMO work. - David to provide the contact?

ONAP and OSM to see how to work together is to be analyzed.

...

    1. 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:

Tag the meeting time to (12:00 pm) UTC that brings it one hour early to the current time and remains in it for the rest of the sessions irrespective of the DST changes.

The attendees on the meeting agreed to tag to UTC.

UTC - 12:00 PM.


Future tasks

  1. 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)
  2. 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
  3. K-Release details
    1. K Release#ServiceManagementandOrchestrationLayer(SMO)

View file
namevideo1386302492.mp4
height250





5th June

TE&IV and SMO discussion continuation

...

  1. O-RAN SMO enhancements - Aarna Networks (Bhanu and Sandeep)
    View file
    nameSMO_Upstream_Aarna.xlsx
    height250

  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

...

  • 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:

DetailsItemWhoNotes




Recording

View file
nameaudio1683193723.m4a
height250
View file
namechat.txt
height250

...