Page History

...

• Cherry Application LCM Step 1 - Create Application Package

• Cherry Application LCM Step 2 - Package Validation

• Cherry Application LCM Step 3 - Catalog Package

• Cherry Application LCM Step 4 - Create Config

• Cherry rAPP Deployment Scenario  (candidate for OSC rel D "Dawn")

• Cherry xAPP Deployment Scenario (candidate for OSC rel D "Dawn")

• Cherry Specifications, YANG Modules, NonFunctional

The implementation of this use case will demonstrate what application developers need to do in order to onboard their application to the SMO. It will also provide orchestration requirements for an SMO implementation in 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, InstanceConfig, 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.

...