...
Near-Real-time RAN Intelligent Controller Platform (E2 Interface) (RICPLT) |
---|
Mission: E2 updates with first E2APv2.0 support and improvements in subscription interface in xapp frameworks. Original primary goals: TODO |
Planned F release highlights TODO |
PTL: Thoralf Czichy |
Status 2022-05-05: From the 28 epics planned (link) we implemented 4 (link). 7 items have been moved out of the F release, e.g, because of implementation delays (link). Incomplete items: 17 (link). Additionally we fixed 17 bugs and small implementation tasks (link) |
F release source code, container images and deployment instructions Code coverage: Code coverage reports (current coverage and list of components that need to set up Jenkins job for auto-generation of the reports as part of CI) |
Operation and Maintenance (OAM) |
---|
Primary Goals: According to the O-RAN-SC-OAM-Architecture document, all ManagedElements (near-real-time-RIC, O-CU-CP, O-CU-UP, O-DU and O-RU) implement the O1-interface. |
F Feature Scope:
|
PTL: Martin Skorupski |
F release source code, container images and deployment instructions (and status) Jira: Count of Epics ( 15 issues ), User Stories, Tasks, and Issues: 166 issues Source Code: Integration: Release notes:
Code coverage:
|
...
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). | ||||||||
F Feature:
| ||||||||
PTL: Mahesh Jethanandani | ||||||||
Status:
Jira: Count of Epics ( 0 issues ), User Stories, Tasks:
and Issues: 6 issues | ||||||||
F release source code, container images and deployment instructions TODO-update Docker image and instruction on how to install SMO O1 NETCONF 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 e-release "https://gerrit.o-ran-sc.org/r/smo/o1mo/o1", whereas the O1/VES repository can be had by "git clone --branch e-release "https://gerrit.o-ran-sc.org/r/smo/ves"
|