Versions Compared

Key

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

...

PROJECT PROPOSAL Service Management and Orchestration (SMO)

O-RAN Software Community Releases Cherry, Dawn, C & D Releases

Project Name:

  • Proposed name for O-RAN SC project: Service Management and Orchestration (SMO)

  • Proposed name Name for the repository: smo

Project description:

...

  • 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 “Minimum Viable Product” (candidate for OSC rel C "Cherry")
    In addition to SMO-dev, a light-ware SMO instance mainly used for facilitating module testing using OTF scripts. It should also include O-RAN-SC simulators to show and validate the entire O-RAN functions. Stretch goal: Inclusion 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-RT-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 commercial products, including “one-click” deployment, geo-redundancy.

...

Project Technical Lead (PTL): to be defined Mahesh Jethanandani

Names, gerrit IDs, and company affiliations of the committers:to be defined – does this project need gerrit/nexus? Or are wiki and doc sufficient?

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 order):to be defined – does this project need gerrit/nexus? Or are wiki and doc sufficient?

Key Subproject Facts

Subproject Name:

JIRA subproject name: smoapp

JIRA subproject prefix: smoapp

Repo name:

smo/app

Lifecycle State: incubation

...