Versions Compared

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 orchestrate and manage different network functions within O-RAN. It supports several interfaces, O1, O2, O1/VES and others. It does this orchestration and management by integrating different software artifacts of existing open-source projects creating to create a fully functional open-source Service Management and Orchestration (SMO). 

F Feature:

The focus of the F-release is around two major interfaces, O1/VES and O2. O1 continues to be a stable interface with no change requirements.

  • O1/VES interface
    • Add support for StdDefined messages.
    • Expand on the list of PM counters supported
  • O2 interface
    • Tacker project will commit VNF support

Status:  

  • O1/VES interface
    • Added support for StdDefined messages
    • Support for PM counters, although this is blocked on the Copyright issue related to 3GPP/O-RAN.
  • O2 interface
    • Tacker project committed. See details below.

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

F 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 Instructions on how to install SMO O1/VES interface can be found here. A video that demonstrates an installation of the solution can be found here. 
  • For the O1 interface the repository can be found at "git clone --branch e-release "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"

...