Welcome to the E release page for the O-RAN Software community.
The E release is currently under development and its source code is maintained within teh master branch of each repo. Once released further instructions related to separate maintenance branches and release image lists will be available here,
Near-Real-time RIC X-APPs (RICAPP) |
---|
Primary Goals: Expand the community working on open source xApps for O-RAN SC. Enhance the set of open source xApps in support of the R-SAC use cases (traffic steering, health check, life cycle management) as well new use cases. Update and enhance existing xApps to take advantage of the new features in xApp SDK (implemented by the xApp frameworks in C++, go, and python). |
E release highlights (7-7-21):
|
PTL: Matti Hiltunen |
Jira: Count of Epics, User Stories, Tasks, and Issues: 165 issues |
Status (5-25-21): E Release status
|
E release source code, container images and deployment instructions Each repository has a branch named "dawn" that can be accessed using git. For example, the source code for the AD xApp can be retrieved using "git clone --branch dawn "https://gerrit.o-ran-sc.org/r/ric-app/ad". The other xApps in the D release can be found at ric-app/qp, ric-app/ts, ric-app/lp, ric-app/hw, ric-app/hw-go, ric-app/hw-python, ric-app/mc, ric-app/bouncer, and scp/ric-app/kpimon. Note that the other ric-app repos are obsolete. Note that this branch is in maintenance and all new development is done in branch "master". In order to deploy the D release xApps, you can re-use the pre-created container images as defined here and the instructions on testing the xApps can be found here. |
Near-Real-time RAN Intelligent Controller Platform (E2 Interface) (RICPLT) |
---|
Mission: TODO Original primary goals: Update to E2APv1.1 (E2 Node configuration transfer in E2 Setup and E2 Configuration Update (even if likely changing again in E2APv2.0) and E2SM OID support in internal E2SM function query interfaces) // TODO // TODO Epics planned: link-TODO and TOOD items as stretch goals: link |
Achieved E release highlights = high-level release notes (TODO) below (note that the release image list is here (once releases): TODO) TODO once released |
PTL: Thoralf Czichy |
Status 2021-09-15: we are working on implementing the planned development items |
E release source code, container images and deployment instructions We again plan to cut a branch from the master branch once the E release is released and goes into maintenance. Also we plan to provide an ready-made container image list. |
Non-Real-time RIC (A1 Interface) (NONRTRIC) |
---|
Primary Goals:
|
E Feature Scope:
|
More detail:
|
PTL: |
Jira:
|
D release source code, container images and deployment instructions
|
Operation and Maintenance (OAM) |
---|
Primary Goals:
|
E Feature Scope:
|
PTL: Martin Skorupski |
E 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: |
Please see: Use Case Flow tests for E-Release |
O-RAN Central Unit (OCU) |
---|
Primary Goals:
|
D Release Feature Scope:
|
PTL: |
Status: Radisys Commercial CU being used as a test fixture. H/W and S/W requirements have been shared and awaiting the same to be configured. |
D release source code, container images and deployment instructions not applicable |
O-DU High |
---|
Primary Goals: New Feature Development
Feature Verification
End to End Integration Support
|
E Feature Scope:
|
PTL: user-30c9d |
Status: Updated: 15th Sept 2021 JIRA: Epics Status below: Updates from HCL: Dependency/Blockers: |
D release source code, container images and deployment instructions |
O-DU Low |
---|
Primary Goals: —Continue O-DU low and O-DU high pairwise test. —FAPI P7 message integration -> Ongoing —Continue O-DU Low and O-RU emulator test. —Further CU plane testing -> Ongoing —Continue E2E test with UE simulator. —Support the UE attachment test —Development activity for Closed Loop Automation use-case —Support and test for cell stop and restart within O-DU High layers |
E Release Feature Scope: |
PTL: Luis Farias , Alternate: @Chenxi Yue |
|
E release source code, container images and deployment instructions TODO |
Simulators (SIM) |
---|
Primary Goals:
|
E Feature Scope: |
PTL: Alex Stancu |
Jira: Count of Epics, User Stories, Tasks, and Issues: 5 issues |
Status: |
E release source code, container images and deployment instructions Docker container images are described here. Each repository has a branch named "dawn" that can be accessed using git: "git clone --branch dawn "https://gerrit.o-ran-sc.org/r/sim/o1-interface". Make sure to replace the URL with correct repositories. Note that this branch is in maintenance and all new development is done in branch "master". The complete list of repositories belonging to the SIM project is here. Deployment instructions here. Please see: Use Case Flow tests for E-Release |
Infrastructure (INF) |
---|
Primary Goals:
|
E release Feature Scope:
|
PTL: Jackie Huang |
Jira: Count of Epics, User Stories, Tasks, and Issues: Update at Test: Release Note: |
E release source code, container images and deployment instructions
|
Integration and Test (INT) |
---|
Primary Goals: To support OSC project CI pipeline. To test and validate the components and use cases |
Feature Scope:
|
PTL: |
Jira: Count of Epics, User Stories, Tasks, and Issues: 54 issues |
E release source code, container images and deployment instructions not applicable |
Documentation (DOC) |
---|
Primary Goals: TODO |
Bronze Feature Scope: TODO |
PTL: weichen ni |
Jira: Count of Epics, User Stories, Tasks, and Issues: |
D release source code, container images and deployment instructions not applicable |
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: |
PTL: Mahesh Jethanandani |
Status: Jira: Count of Epics ( 0 issues ), User Stories, Tasks, and Issues: 6 issues |
D 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. The repository has a branch named "dawn" that can be accessed using git. 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" |