Versions Compared

Old Version 37

changes.mady.by.user peng Lu

Saved on

compared with

New Version 38

changes.mady.by.user John Keeney

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.

J release Feature Scope: 

Improve O2 DMS ETSi profile.

  1. Fault management

Develop O2 interfaces and integrate with OSC INF:

  1. FOCOM interfaces to create cluster.
  2. NFO K8s profile to Deploy a CNF on top of the cluster created through OSC-INF

Develop a Topology & Inventory (TEIV) registry & exposure capability

PTL: Seshu Kumar Mudiganti 

J release highlights/accomplishments ():

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

J 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

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

J 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 epic 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
    serverId5ec52304-b77c-3ce7-af6a-112cb13e6008
    keySMO-146
  • 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
    serverId5ec52304-b77c-3ce7-af6a-112cb13e6008
    keySMO-145
  • 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
    serverId5ec52304-b77c-3ce7-af6a-112cb13e6008
    keySMO-144
  • 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
    serverId5ec52304-b77c-3ce7-af6a-112cb13e6008
    keySMO-135
The status of the SMO project is tracked using Jira items. For the latest status refer to the items below.




Infrastructure (INF)

Primary Goals: 

  • Implement the O-Cloud reference design, provide the real time performance to allow the O-CU, O-DU and other components running on top of it.
  • Provide interaction capabilities with other components.
  • Provide O2 interface and support integration with SMO.

J release Feature Scope:  

  • Update INF Platform to aligned with StarlingX 9.0
  • Update O2 implementation to aligned with new Spec Ver 5.0
  • Develop OKD as alternative O-Cloud platform

PTL: Jackie Huang

J release highlights/accomplishments (  ):

Jira: Status of Epics, User Stories, Tasks, and Issues:

Update at  

  • EPICs:

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 = INF AND issuetype = Epic AND fixVersion = "J Release"
serverId5ec52304-b77c-3ce7-af6a-112cb13e6008

  • Stories:

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
maximumIssues30
jqlQueryproject = INF AND issuetype = Story AND fixVersion = "J Release"
serverId5ec52304-b77c-3ce7-af6a-112cb13e6008

  •  Tasks:

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 = INF AND issuetype = Task AND fixVersion = "J Release"
serverId5ec52304-b77c-3ce7-af6a-112cb13e6008

  •  Bugs:

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
maximumIssues30
jqlQueryproject = INF AND issuetype = Bug AND fixVersion = "J Release"
serverId5ec52304-b77c-3ce7-af6a-112cb13e6008

Test status:

Code coverage:

Release Note:

J release source code, images and deployment instructions

  • Each repository has a branch named "j-release" that can be accessed using git:
  • Images for INF project
  • Deployment instruction: 


...