Versions Compared

Old Version 86

changes.mady.by.user Jackie Huang

Saved on

compared with

New Version 87

changes.mady.by.user Toshiaki Takahashi

Saved on

Key

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

...

Service Management and Orchestration Layer (SMO)

Primary Goals:

The SMO acts as an uber identity that overlooks the different aspects of the O-RAN deployment. Starting with how solutions are deployed, to how they interact with each other, to how they are managed.

G release Feature Scope: 

The focus for the G release in SMO is interoperability. Every sub-project within SMO has at least one item that focuses on interoperating with one other entity outside of SMO. For example,

  • On the O1 interface, the focus is on trying to bring-up O-DU using NETCONF and YANG models defined for O-DU.
  • On the O1/VES interface, it is ability to generate network slicing PM events in the O-DU, and the ability to receive them in SMO dashboard, and store them in InfluxdB.
  • On the O2 interface, it will be the ability to instantiate an instance of a Network Function (NF) like the O-DU in the O-Cloud.

Separate from this, each sub-project within SMO has other features/capabilities it will address as part of the G-release. For details please refer to the minutes of the SMO meeting here.


PTL: Mahesh Jethanandani

G release highlights/accomplishments (December 12, 2022):

  • In the G release, the O1 interface has support for configuration of Network Functions (NF) over NETCONF using YANG models.
  • The O1/VES interface demonstrated interoperability between SMO and O-DU NF.  Network slicing PM events generated by O-DU were captured by the O1/VES collector and displayed on the Grafana dashboard.
  • The O2 interface demonstrated TST010 API Conformance, along with aligning with O2 DMS ETSI NFV Profile

G release source code, container images and deployment instructions (and status)

G release source code for SMO can be found in the following repositories

The container images for SMO can be found on the Nexus server, where applicable.
The container images for OpenStack Tacker can be found in OpenStack Kolla repository.

The OpenStack Tacker container can be started with the steps in the following documentation.

The installation instructions for SMO can be found in the documentation page here.

Status

The status of the SMO project is tracked using Jira items. For the latest status refer to the items below.

 

Jira
serverORAN Jira
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryproject = SMO AND issuetype = Task AND status in ("In Progress", "To Do")
serverId5ec52304-b77c-3ce7-af6a-112cb13e6008

...