Date: Thu, 28 Mar 2024 12:43:30 +0000 (UTC) Message-ID: <1622039226.10127.1711629810411@aws-us-west-2-oran-confluence-1.web.codeaurora.org> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_10126_834015107.1711629810410" ------=_Part_10126_834015107.1711629810410 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
PROJECT PROPOSAL =EF=83=A0 Ser= vice Management and Orchestration (SMO)
O-RAN Software Community, C & D Releases
Project Name:
Proposed name for O-RAN SC project: Service Management and Orches= tration (SMO)
Name for the repository: smo
Project description:
The term =E2=80=9CSMO=E2=80=9D refers to = its definition by the O-RAN Alliance. The primary goal of the SMO project i= s to integrate different software artifacts for existing open-source projec= ts creating a fully functional open-source Service Management and Orchestra= tion (SMO). It is intended to find and document gaps in open-source compare= d to the O-RAN specifications of a SMO. Specification proposals and impleme= ntations showing how to address such gaps will be proposed to related O-RAN= working groups. The objective is to provide documentation and software imp= lementation of integration tested SMO deployment interacting with O-RAN Man= agedElements based on the use cases defined by O-RAN Alliance WG1 UCFG.
The SMO project has strong dependencies t= o
O-RAN-SC projects NON-RT-RIC, OAM, INT, SIM and DOC and to
O-RAN Alliance Working Groups 1, 2, 3 and 6.
Refer to OSC wiki for work completed within previous releases: https://wiki.o-ran-sc.org/display/OAM/SMO+-+S= ervice+Management+and+Orchestration
It is assumed that modern implementations=
of a couple of Linux Foundation Projects are considered creating the funct=
ion of a SMO as defined by O-RAN Alliance
(in alphabetical order):
and many more =E2=80=A6
The SMO project will describe and documen= t the instantiation of different SMO deployment options:
SMO-Dev
A SMO instance which focus on developer experience, used by O-RAN-SC develo=
pers.
(Note: if appropriate, artifacts (code, doc) could move OAM pr=
oject to SMO)
SMO-MVP =E2=80=9CMinimum Viable Product=E2=80=9D (pro for Ch=
erry)
A light-ware SMO instance mainly used for module testing. It should include=
O-RAN-SC simulators to show and validate the entire O-RAN functions
(Note: if appropriate, artifacts (code, doc) could move from Non-RT-RIC an=
d OAM project to SMO
SMO-full (future releases)
A full functional O-RAN-SC SMO instance as reference implementation for com=
mercial products, including =E2=80=9Cone-click=E2=80=9D deployment, geo-red=
undancy, ...)
Scope:
The following features are in scope for the SMO project within O-RAN SC = release Cherry:
Demonstration of Pre-O2 LCM feature
Cherry Applicati= on LCM Step 1 - Create Application Package
Cherry r= APP Deployment Scenario (candidate for OSC rel D "Dawn")= p>
Cher= ry xAPP Deployment Scenario (candidate for OSC rel D "Dawn")
=The implementation of this use case will demonstrate what applicati= on developers need to do in order to onboard their application to the SMO. = It will also provide orchestration requirements for an SMO implementation i= n order to manage an onboarded application through its Life Cycle.
SMO-Dev (for developers only)
Update existing A1 (Rest), O1 (NetConf, VES, FTPes) so, Pre-O2, ModelCatalog, ServiceConfig, VirtualInventory and OTF =
test harness
SMO-MVP =E2=80=9CMinimum Viable Product=E2=80=9D (c=
andidate for OSC rel C "Cherry")
In addition to SMO-dev, a light-ware SMO instance mainly used for facilitat=
ing module testing using OTF scripts. It should also include O-RAN-SC simul=
ators to show and validate the entire O-RAN functions. Stretch goal: Inclus=
ion of ML training for xApps and rApps that use AI/ML components in the SMO=
.
(Note: if appropriate, artifacts (code, doc) could move from Non-R=
T-RIC and OAM project to SMO)
SMO-full (candidate for OSC rel D "Dawn")
A full functional O-RAN-SC SMO instance as reference implementation for com=
mercial products, including =E2=80=9Cone-click=E2=80=9D deployment, geo-red=
undancy.
Please see (draft - will be updated)
SMO in O-RAN architecture =E2=80=93 Source: O-RAN-SC OAM
Resources:
Project Technical Lead (PTL): Mahesh Jethanandani
Names, gerrit IDs, and company affiliations of the committers:
Mahesh Jethanandani (committer), mjethanandani, VMware.=
Santanu De (contributor), santanude, Xoriant Systems
Sriram Rupanagunta (contributor), sriramrupanagunta, Aarna Networks
Sandeep= Sharma (contributor), sandeepaarna, Aarna Networks
Names and affiliations of any other contributors (in alphabetical ord= er):
Key Subproject Facts
Subproject Name:
JIRA subproject name: app
JIRA subproject prefix: app
Repo name:
smo/app
Lifecycle State: incubation