Versions Compared

Version Old Version 52 New Version 53
Changes made by

Ankit Barve

Seshu Kumar Mudiganti

Saved on

Key

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

...

Service Management and Orchestration Layer (SMO)

Primary Goals:

The primary goal of SMO in the H-release is to act as glue between the different components of O-RAN.

H release Feature Scope: 

The scope for H-release includes homing. In addition, package management includes inventory and image management.PTL: Mahesh Jethanandani Alignment with O-RAN O2 DMS ETSI NFV Profile.

PTL: Seshu Kumar Mudiganti 

H release highlights/accomplishments (June, 2023):

  • TODOAutomated API Conformance testing
  • Alignment with O-RAN O2 DMS ETSI NFV Profile.
  • Refresh SDNR image to the latest on SMO O1 project.

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

H 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 Legacy
serverSystem 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")
serverId3122c0e4-6090-3a7d-9725-8b5a32a8eaeb

...