Welcome to the E release page for the O-RAN Software community.
The E release is currently under development completed and its source code is maintained within the master branch of each repo. Once released further instructions related to separate maintenance branches and The release image lists will be available here,and source code can be found here for each projects.
Table of Contents
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, network slicing) 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 plan (12-01-21):
|
PTL: SUNIL SINGH (former PTL still helping out: Matti Hiltunen) |
Jira: Count of Epics, User Stories, Tasks, and Issues: 165 issues |
Status E release highlights/accomplishments (12-0114-21):
|
E release source code, container images and deployment instructions Will be provided when E Release is ready. |
Near-Real-time RAN Intelligent Controller Platform (E2 Interface) (RICPLT)
Mission: E2 updates with first E2APv1.1 support and improvements in E2 subscription handling.
Original primary goals: Update to E2APv1.1 (E2 Node configuration transfer in E2 Setup and E2 Configuration Update (RIC-638, even if likely changing again in E2APv2.0) and E2SM OID support in internal E2SM function query interfaces (RIC-640)) // RIC-809 Subscription manager to delete subscriptions in case of E2 disconnect (incl. Xapp changes) // RIC-796 sub mgr and xapp-frame error cases // RIC-793 Prevent A1 Job ID conflicts from multiple RICs using the same A1 producer (SMO) // Partial only: RIC-647 (first step of reimplementation A1 mediator in golang to avoid A1 being the only python container in RIC platform // RIC-709 E2 stats exposing individual counters instead of groups // RIC-714 support for DMS REST interface in addition to DMS CLI // RIC-113 DB: SDL CLI for debugging and testing // RIC-110 FindKeys/GetAllKeys SDL API to support glob-style patterns // RIC-676 Update to Ubuntu 20.04 as base image for all containers // improvements in xApp testing // 29 Epics planned: link and 30 items as stretch goals: link
Achieved E release highlights = high-level release notes (2021-12-03) below (note that the release image list is here: link)
- we updated from E2APv1.0 to E2APv1.1. The platform now stores OIDs (introduced in E2APv1.1) for the E2SM of E2 function definitions in RNIB. Since E2APv1.1 is backwards compatible with 1.0, you can still connect E2 nodes that support E2APv1.0. Note that for the next release we plan to switch to E2APv2.0 only.
- The E2 subscription manager now automatically deletes its stored subscriptions if it gets notified (by the E2 manager) of E2 nodes having disconnected. xApps are expected to do the same and need to re-issue their subscriptions once the E2 node is reconnected. This behavior is different to earlier behavior where the subscription manager kept the subscriptions in such situations. Note that the standard requires the E2 node to delete its subscriptions if there's the E2 interface is disconnected.
- The E2 subscription manager now handles various error scenarios that previously were not handled.
- We will continue the re-implementation of the A1 mediator in golang in release F. The first parts are already implemented, but in the E release we stay with the "old" python-implementation of the A1 mediator.
- On SDL side we now have a SDL CLI that can be used in testing (instead of direct usage of the Redis CLI). The SDL API for findkeys/getkeys now supports glob-style patterns.
- The golang SDL API/library now handles namespaces as part of its function signatures instead of this being a global parameter. This eases usage of multiple namespaces from the same application.
For the E release of the near-RT RIC we did only limited integration testing: only the use cases: deploy RIC, deploy xApp and make E2 connection were tested.
Filled in end-of-release checklist : Release criteria checklist - Release E
PTL: Thoralf Czichy
Status 2021-12-08: we are working on implementing the last planned development items below. From the 29 epics planned (link) we implemented so far 13 (link). 13 items have been moved out of the E release, e.g, because of implementation delays (link). We expect 3 items to still complete (link).
- RIC-816 → review ongoing (change does not require image any rebuild): https://gerrit.o-ran-sc.org/r/c/ric-plt/ric-dep/+/7275
- RIC-779 → review ongoing (change does not require an image rebuild): https://gerrit.o-ran-sc.org/r/c/it/test/+/7270/1
- RIC-113 (DB) - expected to complete in week 50 (starting dec-13), but we can generate new dbaas image (which includes the sdlcli addition). Petri O is working on this. Since dbaas image is somwhat independent of all others, this should be fine,
E release source code, container images and deployment instructions
Each repository has a branch named "e-release" that can be accessed using git: "git clone --branch e-release "https://gerrit.o-ran-sc.org/r/ric-plt/e2". 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 RIC platform is defined here: Scope of the near-RT RIC platform and its components (summary).
In order to deploy the E release of the near-RT RIC platform you can re-use the pre-created container images as defined here. The same instructions as always apply, i.e., follow the general latest instructions: https://docs.o-ran-sc.org/projects/o-ran-sc-ric-plt-ric-dep/en/latest/ → Installing Near Realtime RIC in RIC Cluster, but make sure to use "git clone --branch e-release ..." instead of "git clone ..." when cloning it/dep and ric-plt/ric-dep.
Non-Real-time RIC (A1 & R1 Interfaces) (NONRTRIC)
- The primary goal of Non-RT RIC is to support intelligent RAN optimization by providing policy-based guidance, ML model management and enrichment information to the near-RT RIC function so that the RAN can optimize, e.g., RRM under certain conditions.
- It can also perform intelligent radio resource management function in non-real-time interval (i.e., greater than 1 second).
- Non-RT RIC can use data analytics and AI/ML training/inference to determine the RAN optimization actions for which it can leverage SMO services such as data collection and provisioning services of the O-RAN nodes.
- Non-RT-RIC will define and coordinate rApps (Non-RT-RIC applications) to perform Non-RT-RIC tasks.
- Non-RT-RIC will also host the new R1 interface (between rApps and SMO/NONRTRIC services)
E Feature Scope / Achievements:
- E Release Priorities:
- ONAP Control Loop -> O-RAN rApp : “The rApp-ification of ONAP Control Loops”
- Adopt ONAP CL work as a starting point, continue to identify gaps, then extend
- Identify & motivate where an rApp is different from a CL
- Types of rApps:
- Microservice-based rApps
- Non-Microservice-based rApps
- NONRTRIC Service Exposure/Gateway -> O-RAN R1 : “The R1-ification of Service Exposure”
- Service-independent aspects
- Types of exposure support in R1:
- Microservice-based rApps & Service
- Non-Microservice-based rApps & Service
- Use cases of rApps & Exposing specific Services via R1
- Requirements drivers & demonstrators
- O-RU FH recovery (multiple), O-DU Slice Assurance (multiple), Existing Function Tests, various other use cases in ONAP
- Continued Evolution & Support for A1 functions
- ONAP Control Loop -> O-RAN rApp : “The rApp-ification of ONAP Control Loops”
- NONRTRIC Functions:
- Integrated A1 Adapter from ONAP (A1 Policy (A1-P) controller – mediation)
- Integrated A1 Policy Management Service from ONAP (A1 Policy (A1-P) controller)
- rApp/Control Loop Manager (ONAP & OSC)
- OSC Information Coordinator (controller – Data Management & Exposure & A1 Enrichment Information (A1-EI) Job management)
- OSC Non-RT-RIC Control Panel (GUI – for A1-P & A1-EI Job management)
- OSC A1 Simulator (a stateful test stub to simulate near-RT-RIC end of A1 interface – A1-P & A1-EI)
- Initial OSC APP catalog (for registering/querying APPs)
- K8S Helm Chart LCM Manager - for APP µServices etc. (ONAP & OSC)
- Exposure Gateway Functions
- Coordinated service exposure for R1 interface
- DMaaP → Information producer Mediator/Adapter (multiple)
- PM File Job Manager (ONAP & OSC)
- E Release: discussions: (NONRTRIC Wiki Release E)
- E Release: How to build: (NONRTRIC Wiki Release E - Build)
- E Release: How to run: (NONRTRIC Wiki Release E - Run)
PTL:
Jira:
- Count of Epics (20 issues), User Stories, Tasks, and Issues: (455 issues)
- nonrtric : https://gerrit.o-ran-sc.org/r/admin/repos/nonrtric
- portal/nonrtric-controlpanel : https://gerrit.o-ran-sc.org/r/admin/repos/portal/nonrtric-controlpanel
- sim/a1-interface : https://gerrit.o-ran-sc.org/r/admin/repos/sim/a1-interface
Operation and Maintenance (OAM)
Primary Goals:
- Support of RSAC VES architecture updates
- Deployment of VES-Collector and Message Bus at the edge
- Support of O-DU use case ()
- Definition of the to be used yang model.
- Support of pre-spec PM streaming - VES like approch (see https://wiki.o-ran-sc.org/download/attachments/35881433/E_rel_v3.pptx?api=v2 page #97)
- creation of a CR to WG10 OAM Interface Specification - "Model-driven PM streaming"
See more details on OAM wiki: E-Release
E Feature Scope:
- Switch to Opendaylight version Silicon-SR2
- Standard-defined VES for
- NotifyNewAlarm
- NotifyAlarmCleared
- NotifyHeartbeat
- NotifyMoiChanges
PerfDataStreamingMNS(does not include measurements - therefor a O-RAN-SC specific message-body required - ...hello-world.oas3.yaml)
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:
- to be done
Release notes:
- in docs: docs.o-ran-sc.org/oam/release-notes (latest)
- in wiki: E-Release notes
O-RAN Central Unit (OCU)
- In the absence of O-CU, Radisys commercial CU image to be used for E2E testing
D Release Feature Scope:
- Radisys Commercial CU being used as a test fixture for E2E testing
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
Support for Multi UE (Connected = 16, Active =4, Per Slot = 1)
- Only slot based round robin scheduling support for multi UE scheduling
Support for Multi Bearer
- Basic RAN slicing support
- Support for HARQ
Feature Verification
- Closed Loop Automation Feature Verification
- 16 QAM and 64 QAM Support Verification
End to End Integration Support
TDD/Mu1/100MHz
FDD/Mu0/20MHz * (Spillover from D release)
E Feature Scope:
Support for Multi UE (Connected = 16, Active =4, Per Slot = 1)
- Only slot based round robin scheduling support for multi UE scheduling
Support for Multi Bearer
- Basic RAN slicing support
- Support for HARQ
- End to End Integration Support (TDD and FDD stack validation)
- Closed Loop Automation Feature Verification
PTL: user-30c9d
Status:
12/08/2021:
Support for Multi UE feature
Jira:
https://jira.o-ran-sc.org/browse/ODUHIGH-352
Status
Completed
Support for Multi Bearer feature
Jira:
https://jira.o-ran-sc.org/browse/ODUHIGH-357
https://jira.o-ran-sc.org/browse/ODUHIGH-358
https://jira.o-ran-sc.org/browse/ODUHIGH-359
Status
Completed
Support for Basic RAN Slicing feature
Jira:
https://jira.o-ran-sc.org/browse/ODUHIGH-365
https://jira.o-ran-sc.org/browse/ODUHIGH-366
https://jira.o-ran-sc.org/browse/ODUHIGH-368
https://jira.o-ran-sc.org/browse/ODUHIGH-369
https://jira.o-ran-sc.org/browse/ODUHIGH-371
https://jira.o-ran-sc.org/browse/ODUHIGH-375
https://jira.o-ran-sc.org/browse/ODUHIGH-377
https://jira.o-ran-sc.org/browse/ODUHIGH-378
https://jira.o-ran-sc.org/browse/ODUHIGH-379
https://jira.o-ran-sc.org/browse/ODUHIGH-381
https://jira.o-ran-sc.org/browse/ODUHIGH-389
Status
Completed
Support for HARQ
Jira:
https://jira.o-ran-sc.org/browse/ODUHIGH-356
Status
Deferred to F-Release
Support for E2E Integration support and Validation
Jira:
https://jira.o-ran-sc.org/browse/ODUHIGH-269
Status
Deferred to E-Release maintenance
Support for Closed Loop Automation Feature Validation
Jira:
Deferred to E-Release maintenance
Dependency/Blockers:
Blocked for PTP grandmaster at OSC lab to start the end to end integration activities
Updated: 17 Nov 2021
JIRA: Epics Status below:
- https://jira.o-ran-sc.org/browse/ODUHIGH-357 - Done
- Study for creation of multiple bearers
- https://jira.o-ran-sc.org/browse/ODUHIGH-365 - Done
- Study and Design for Requirements for 3gpp functionality for slicing support
- https://jira.o-ran-sc.org/browse/ODUHIGH-366 - Done
- Study and Design for Requirements [3gpp functionality for slicing support ]
- https://jira.o-ran-sc.org/browse/ODUHIGH-358 - Done
- Support for more than one DRB in UE context Setup Request
- https://jira.o-ran-sc.org/browse/ODUHIGH-369 - Done
- Support for Slice Configuration (3gpp functionalities)
- https://jira.o-ran-sc.org/browse/ODUHIGH-356 - In Progress
- Feature study and design for HARQ
- https://jira.o-ran-sc.org/browse/ODUHIGH-352 - In progress
- Support for multiple UE
- https://jira.o-ran-sc.org/browse/ODUHIGH-359 - Done
- Support to add and modify more than one DRB in UE context Mod Request
- https://jira.o-ran-sc.org/browse/ODUHIGH-377 - Done
- As an O-DU L2 developer, I want to understand the RRM policy application in Scheduler to support RAN Slicing
- https://jira.o-ran-sc.org/browse/ODUHIGH-368 - Done
- Slice information associated during PDU session establishment procedure
- As an O-DU L2 developer, I want to support Slice related Configuration
|
E release source code, container images and deployment instructions Each repository has a branch named "e-release" that can be accessed using git. For example, the source code for the AD xApp can be retrieved using "git clone --branch e-release "https://gerrit.o-ran-sc.org/r/ric-app/ad". The other xApps in the E 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, ric-app/rc, 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 E 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: E2 updates with first E2APv1.1 support and improvements in E2 subscription handling. Original primary goals: Update to E2APv1.1 ( |
Achieved E release highlights = high-level release notes (2021-12-03) below (note that the release image list is here: link)
For the E release of the near-RT RIC we did only limited integration testing: only the use cases: deploy RIC, deploy xApp and make E2 connection were tested. Filled in end-of-release checklist : Release criteria checklist - Release E |
PTL: Thoralf Czichy |
Status 2021-12-08: From the 29 epics planned (link) we implemented 16 (link). 13 items have been moved out of the E release, e.g, because of implementation delays (link). Incomplete items: 0 (link). |
E release source code, container images and deployment instructions Each repository has a branch named "e-release" that can be accessed using git: "git clone --branch e-release "https://gerrit.o-ran-sc.org/r/ric-plt/e2". 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 RIC platform is defined here: Scope of the near-RT RIC platform and its components (summary). In order to deploy the E release of the near-RT RIC platform you can re-use the pre-created container images as defined here. The same instructions as always apply, i.e., follow the general latest instructions: https://docs.o-ran-sc.org/projects/o-ran-sc-ric-plt-ric-dep/en/latest/ → Installing Near Realtime RIC in RIC Cluster, but make sure to use "git clone --branch e-release ..." instead of "git clone ..." when cloning it/dep and ric-plt/ric-dep. If you clone it/dep and use the "ric-dep" as submodule, make sure to run: "cd ric-dep; git checkout e-release" after "git submodule update --init --recursive --force" |
Non-Real-time RIC (A1 & R1 Interfaces) (NONRTRIC) |
---|
Primary Goals:
|
E Feature Scope / Achievements:
|
PTL: |
Jira:
|
- As an O-DU L2 developer, I want to implement O-DU Scheduler algorithm for scheduling DL packet as per RRM policy
|
- As an O-DU L2 developer, I want to implement slice Information/Mapping to RLC DB
|
- As an O-DU L2 developer, I want to implement automatic PRB allocation per DL slot using Bitmap
|
- As an O-DU L2 developer, I want to implement automatic PRB allocation per UL slot using Bitmap
|
- As an O-DU L2 developer, I want to implement application of slice configuration received over O1 interface
|
- As an O-DU L2 developer, I want to implement UL/DL Throughput calculation Per Slice
|
|
Operation and Maintenance (OAM) |
---|
Primary Goals:
|
- As an O-DU L2 developer, I want to implement SMO/O1 sends REconfiguration with Optimized RRM Policy
- As an O-DU L2 developer, I want to implement DL Throughput calculation Per Slice
Updates from HCL:
- https://jira.o-ran-sc.org/browse/ODUHIGH-362
- Finalizing cell configuration parameters - In Progress
- https://jira.o-ran-sc.org/browse/ODUHIGH-383
- Cell and Network slicing configuration over O1 - In Progress
- https://jira.o-ran-sc.org/browse/ODUHIGH-384
- VES PM data for slicing use case - In Progress
Dependency/Blockers:
Blocked for PTP grandmaster at OSC lab to start the end to end integration activities
Updated: 10 Nov 2021
JIRA: Epics Status below:
See more details on OAM wiki: E-Release |
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:
|
- Study for creation of multiple bearers
- Study and Design for Requirements for 3gpp functionality for slicing support
- Study and Design for Requirements [3gpp functionality for slicing support ]
- Support for more than one DRB in UE context Setup Request
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 on 12/15/2021 JIRA REFERENCE 1) Support for Multi bearers ODUHIGH-369 - Done
https://jira.o-ran-sc.org/browse/ODUHIGH- 380 - DoneAs an O-DU L2 developer, I want to implement automatic PRB allocation per DL slot using BitmapStatus: Completed 2) Support for Multi UE https://jira.o-ran-sc.org/browse/ODUHIGH- 385 - DoneAs an O-DU L2 developer, I want to implement automatic PRB allocation per UL slot using BitmapStatus: Completed 3) Network Slicing support https://jira.o-ran-sc.org/browse/ODUHIGH- 375 - to be startedAs an O-DU L2 developer, I want to implement application of slice configuration received over O1 interfaceStatus: Completed 4) Resource allocation in time domain changes to meet flexible k0, k1 and k2 values https://jira.o-ran-sc.org/browse/ODUHIGH- 378 - DoneAs an O-DU L2 developer, I want to implement UL/DL Throughput calculation Per SliceStatus: Completed 5) Support for cell configuration over O1 interface https://jira.o-ran-sc.org/browse/ODUHIGH- 379 - to be started
Status: Completed 12/08/2021: Support for Multi UE feature Jira: Updates from HCL: https://jira.o-ran-sc.org/browse/ODUHIGH- 362
Status Completed Support for Multi Bearer feature Jira: https://jira.o-ran-sc.org/browse/ODUHIGH- 383
://jira.o-ran-sc.org/browse/ODUHIGH- 384
Dependency/Blockers: Blocked for PTP grandmaster at OSC lab to start the end to end integration activities Updated: 20 Oct 2021 JIRA: Epics Status below:
https://jira.o-ran-sc.org/browse/ ODUHIGH-357 - Done
Status Completed
Support for Basic RAN Slicing feature Jira: https://jira.o-ran-sc.org/browse/ODUHIGH-365 - Done
https://jira.o-ran-sc.org/browse/ODUHIGH-366 - Done
https://jira.o-ran-sc.org/browse/ODUHIGH- 358 - Done
https://jira.o-ran-sc.org/browse/ODUHIGH-369 - In Progress
https://jira.o-ran-sc.org/browse/ODUHIGH- 356 - In Progress
https://jira.o-ran-sc.org/browse/ODUHIGH- 359 - In Progress
https://jira.o-ran-sc.org/browse/ODUHIGH- 368 - Done
https://jira.o-ran-sc.org/browse/ODUHIGH- 369 - Done
https://jira.o-ran-sc.org/browse/ODUHIGH-381 - WIP
https://jira.o-ran-sc.org/browse/ODUHIGH-389 Status Completed Support for HARQ Jira: https://jira.o-ran-sc.org/browse/ODUHIGH- 371 - WIP
Status Deferred to F-Release Support for E2E Integration support and Validation Jira: https://jira.o-ran-sc.org/browse/ODUHIGH- 380 - WIPAs an O-DU L2 developer, I want to implement automatic PRB allocation per DL slot using BitmapStatus Deferred to E-Release maintenance Support for Closed-Loop Automation Feature Validation Jira: Deferred to E-Release maintenance Dependency/Blockers: Blocked for PTP grandmaster at OSC lab to start the end to end integration activities HCL's update Support for Basic RAN Slicing feature - O1 interface Jira: https://jira.o-ran-sc.org/browse/ODUHIGH -385 - WIPAs an O-DU L2 developer, I want to implement automatic PRB allocation per UL slot using Bitmaphttps://jira.o-ran-sc.org/browse/ODUHIGH-383 https://jira.o-ran-sc.org/browse/ODUHIGH-384 Status Completed e-release maintenance activity 375 - to be started
Jira: https://jira.o-ran-sc.org/browse/ODUHIGH- 378 - to be started
395 (Optimization, scaling and rework) https://jira.o-ran-sc.org/browse/ODUHIGH- 379 - to be started
Updates from HCL: https://jira.o-ran-sc.org/browse/ODUHIGH-397 https://jira.o-ran-sc.org/browse/ODUHIGH- 362
https://jira.o-ran-sc.org/browse/ODUHIGH-399 https://jira.o-ran-sc.org/browse/ODUHIGH- 383
https://jira.o-ran-sc.org/browse/ODUHIGH- 384VES PM data for slicing use case - In ProgressStatus Completed Dependency/Blockers: BlockedBlocked for PTP grandmaster at OSC lab to start the end to end integration activities Updated: 15th Sept 2021 JIRA: Epics Status below: | |||||
E release maintenance source code, container images, and deployment instructions e-release maintenance source code: https:// | jirabrowse | ODUHIGH-357 - Done | jira | /browse/ODUHIGH-365 - Done | /projects/o-ran-sc-o-du-l2/en/latest/release-notes.html#e-release |
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 |
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:
Status
E release source code, container images and deployment instructions
TODO
Simulators (SIM)
Primary Goals:
- Support rapid prototyping by providing simulated interfaces
E Feature Scope:
- Support of O-RAN-SC E-Release Network Slicing use case by Radisys - support of O-DU projects for end-to-end closed loop use cases for RAN network slicing (implement any message flows in the O-DU Simulator, if needed)
- Align O1 Simulator with the latest specifications released by O-RAN Alliance.
- Support of NETCONF CallHome via TLS, for the O1 simulator
- VES stdnDefined implementation
PTL: Alex Stancu
Jira: Count of Epics, User Stories, Tasks, and Issues: 5 issues
Status:
E release source code, container images and deployment instructions
TODO
Source code: https://gerrit.o-ran-sc.org/r/gitweb?p=sim%2Fo1-interface.git;a=shortlog;h=refs%2Fheads%2Fe-release Container images are described here: Simulation (E-Release) Instructions: Network Slicing Use Case |
Infrastructure (INF) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Primary Goals:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
E release Feature Scope:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
PTL: Jackie Huang | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
E release highlights/accomplishments ( ):
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Infrastructure (INF) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Primary Goals:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
E release Feature Scope:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Jira: Count of Epics, User Stories, Tasks, and Issues: Update at 02
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Test status:
| bare metal (HP DL380p Gen8) with defects
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Release Note: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
E release source code, images and deployment instructions | TODO: update the sample test process in: Getting Start/Sample test process - Infrastructure - Confluence (
| )
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:
A full integration of all OSC components are not ready yet. Within E release timeframe only limited integration tests were performed across OSC sub-modules, and around the network slicking use case. |
PTL: James Li |
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: In E-release, SMO will be
| ||||||||
PTL: Mahesh Jethanandani | ||||||||
Status: Jira: Count of Epics ( 0 issues ), User Stories, Tasks:
and Issues: 6 issues | ||||||||
E release source code, container images and deployment instructions 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 (when a release has been created) "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" |
...