Versions Compared

Old Version 28

changes.mady.by.user Martin Skorupski

Saved on

compared with

New Version 29

changes.mady.by.user Mahesh Jethanandani

Saved on

Key

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

...

Service Management and Orchestration  (SMO)

Primary Goals: The primary goal of the SMO project is to integrate different software artifacts of existing open-source projects creating a fully functional open-source Service Management and Orchestration (SMO). 

D Feature Scope:

  • Support for O1 interface
    • Implementation of NETCONF client in SMO
    • Reference implementation of a NETCONF server that O-RAN Network Functions, e.g. Near-RT RIC, CU, DU and RU can use. The code can be found at https://github.com/CESNET/netopeer2
    • A minimal set of YANG models that demonstrate the capability of the O1 interface while satisfying the closed-loop automation use-case.
  • Support for O1/VES interface
    • Demonstrate the capability to receive VES events, collect them in a dB, and display them in a dashboard.

PTL: Mahesh Jethanandani 

Status:  

  • An implementation of the O1 interface has been checked into Gerrit. Check out this repo. It has been tested on Ubuntu Linux version 20.04. Feedback is appreciated on other versions and operating systems. Note, this commit is not feature compatible with the O1 interface in other implementations. Some of those features have been identified and marked as enhancements in either this or the next release.
  • An implementation of the VES interface based on schema version 7.2.1, with backward compatibility to 7.0, has been submitted for Gerrit review, and review comments have been provided. Author has updated the commit based on the comments. Waiting on more reviews. Again, the commit is not feature compatible with VES interface in other implementations. Some of those features have been identified and will be added in this or the next release
  • Preliminary version of the YANG models proposed by Martin Skorupski. Currently under review.
  • Have a standalone implementation of the O1/VES interface that not only generates events, but collects them, stores in Influx dB and displays it on a Grafana dashboard. Need to integrate with the rest of the solution.

Jira: Count of Epics ( 0 issues ), User Stories, Tasks, and Issues:  6 issues


...