...
Service Management and Orchestration (SMO) | ||||||||
|---|---|---|---|---|---|---|---|---|
| Primary Goals: The primary goal of the SMO project is to integrate different software artifacts of existing open-source projects creating a fully functional open-source Service Management and Orchestration (SMO). | ||||||||
E Feature Scope: In E-release, SMO will be extended to support network slicing. In particular, RSAC has come up with closed loop automation use case for network slicing which involves the SMO collecting PM counters related to network slicing, and based on them breaching some thresholds will cause a change in the configuration of the network slice. That means the SMO has to have support for PM counters related to network slicing, and an ability to reconfigure the O-DU for the network slice. Separately, AT&T has asked for a disaggregated VES solution that separates the collection of VES events from how it is presented to any application that wants to view them. | ||||||||
PTL: Mahesh Jethanandani | ||||||||
Status: Jira: Count of Epics ( 0 issues ), User Stories, Tasks (
| ||||||||
E release source code, container images and deployment instructions Docker image and instruction on how to install SMO O1 interface can be found here. Docker image for instructions on how to install SMO O1/VES interface can be found here. For the O1 interface the repository can be found at "git clone --branch dawn "https://gerrit.o-ran-sc.org/r/smo/o1mo/o1", whereas the O1/VES repository can be had by "git clone --branch dawn "https://gerrit.o-ran-sc.org/r/smo/ves" |
...