Versions Compared

Old Version 66

changes.mady.by.user Matti Hiltunen

Saved on

compared with

New Version 67

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

E Feature Scope: In E-release, SMO will be

  • SMO was extended to support network slicing. In particular, RSAC has come up with closed loop automation use case for network slicing which involves the SMO collecting PM counters related to network slicing, and based on them breaching some thresholds will cause a change in the configuration of the network slice. That means the SMO
has
  • had to have support for PM counters related to network slicing, and an ability to reconfigure the O-DU for the network slice.
  • Separately,
AT&T has asked for
  • SMO now implements a disaggregated VES solution that separates the collection of VES events from how it is presented to any application that wants to view them. In particular, all events now get posted on the Kafka bus, and different "connectors" are provided to make the data available in different formats. For example, the "DMaaP Connector" provides an ability for a application to read the message in DMaaP format. Alternatively, if the data needs to be synced to a dB, the "InfluxdB Connector" sinks the data to an InfluxdB.

PTL: Mahesh Jethanandani 

Status:  

Jira: Count of Epics ( 0 issues ), User Stories,

Tasks:

Jira
serverORAN Jira
jqlQueryproject = SMO AND issuetype = Task AND status in ("In Progress", "To Do")
serverId5ec52304-b77c-3ce7-af6a-112cb13e6008

and Issues:  6 issues

E release source code, container images and deployment instructions

Docker image and instruction on how to install SMO O1 NETCONF interface can be found here.

Docker image for instructions on how to install SMO O1/VES interface can be found here.

For the O1 interface the repository can be found at "git clone --branch e-release (when a release has been created) "https://gerrit.o-ran-sc.org/r/smo/o1mo/o1", whereas the O1/VES repository can be had by "git clone --branch e-release "https://gerrit.o-ran-sc.org/r/smo/ves"

...