K Release

optimization

Welcome to the K release page for the O-RAN Software community.

The K release is currently in incubation; initiating the definition of the requirements

        

Non-Real-time RIC (NONRTRIC)

K-Release - Highlights:

K Release - Tasks:

Wiki: https://lf-o-ran-sc.atlassian.net/wiki/display/RICNR/

Latest Architecture: 

Components: 

Tasks / Backlog / JIRA: https://jira.o-ran-sc.org/projects/NONRTRIC/issues

Gerrit / Source Code:

Sonar / Test Coverage Reports

Docs:

Testing:

Studies

Weekly Meetings:

Release K - Demos


Release K - Container images

Release K - Deployment Instructions

Near-Real-time RIC X-APPs (RICAPP)

Primary Goals:  

K release plan: 

wiki: RIC Applications (RICAPP) - RIC Applications - Confluence (o-ran-sc.org)

Latest Architecture: Architecture - RIC Applications - Confluence (o-ran-sc.org)

Components: 

Tasks / Backlog / JIRA: Near Realtime RAN Intelligent Controller Applications - ORAN Jira (o-ran-sc.org)

Gerrit / Source Code:

Jira: Count of Epics, User Stories, Tasks, and Issues:  Total (10)

K release highlights/accomplishments:

K release source code, container images and deployment instructions

The list of container images 

Code Coverage Reports : 

Near-Real-time RAN Intelligent Controller Platform (E2 Interface) (RICPLT)

Original primary goals based on contributions from Nokia, Samsung, Capgemini, Alexandre Huff (UTFPR), GS Lab and Abhijit G:

Link to planned Jira work items: link

Achieved K release highlights = high-level release notes (2023-06-20) below (note that the release image list is here: link)



Filled in end-of-release checklist: 

Status 2024-01-05: 


K release source code, container images and deployment instructions

The list of container images for the release ...

Code coverage: 

Mapping of new features to O-RAN Spec


Operation and Maintenance (OAM)

Primary Goals:

  • update of O-RAN WG10 VES message bodies
  • update of O-RAN WG4 optional VES bodies
  • update of OAM-Controller to OpenDaylight version Potassium-SR3 (https://docs.opendaylight.org/en/latest/downloads.html)
  • support of other O-RAN-SC projects (e.g. SMO, Non-RT-RIC, O-DU, INT, SIM) based on RSAC and other input.
  • support of OAI and nephio integration with O-RAN-SC related to OAM in collaboration with O-RAN OSFG.

K release Feature Scope

Please see also project wiki for further details: K-Release

K release highlights/accomplishments (2024-12-06):

Please see release details:


K 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:

O-RAN Central Unit (OCU)

Primary Goals:

  • In the absence of O-CU, Radisys commercial CU image is to be used for E2E testing

K release Feature Scope

K Release Feature Scope: 

  • NA

PTL: 

NA

O-DU High (ODUHIGH)

Primary Goals:

1. End-to-end integration 

2. OSC-OAI Collaboration

3. nFapi interface development

4. Containerization of ODU, CU stub & RIC stub

K release Feature Scope

PTL:  Ankit Barve 

Status on  

K release highlights/accomplishments ():

  • K release source code, container images, and deployment instructions (and status)

source code: 
Release notes: 
Document: 
Code coverage: NA (Unit test framework not available)

O-DU Low (ODULOW)

Primary Goals:

Improve O2 DMS ETSi profile

K release Feature Scope


PTL:  Lvfarias (Deactivated) , Alternate: @Chenxi Yue

K release highlights/accomplishments ():


K release source code, container images, and deployment instructions (and status)

source code: 
Release notes: 
Document: 
Code coverage: 

Simulators (SIM)

Primary Goals:

  • Keep alignment with latest O-RAN specifications (O1, E2)
  • Focus on hybrid and hierarchical OAM architecture 

K Feature Scope / Achievements:

Sprint Demos:

Jira: Count of Epics, User Stories, Tasks, and Issues: 

K release highlights/accomplishments ( ):

K release source code, container images and deployment instructions

Source code:

Container images are described here.

Instructions: no specific instructions.

Code coverage: in progress (sonar for C/C++ code in LF repos).

Service Management and Orchestration Layer (SMO)

Primary Goals:

The primary goal of SMO in the H-release is to act as glue between the different components of O-RAN.

K release Feature Scope

Improve O2 DMS ETSi profile.

improve the NFO K8s profile integration with OSC-INF.

K release highlights/accomplishments ():

Showcased the demos for the Montreal F2F

  1. Topology Exposure & Inventory (TEIV)
    1. TE&IV demo (may be through simulators) - John K
    2. https://lf-o-ran-sc.atlassian.net/wiki/download/attachments/13568120/20241030-OSC-SMO-TEIV-Intro%2BDemo-MontrealF2F2024-JohnKeeney.pdf?version=1&modificationDate=1730715717979&cacheVersion=1&api=v2
  2. SMO O2 (FOCOM and NFO (K8s)) demo of the IMS and DMS (as a possibility) - Shashi and Vamshi
    1. https://drive.google.com/drive/folders/1kWhqy219L2kebXfBf2Q9lUyY2pkXDiyp 
  3. Nephio integration with the OSC-SMO (as a stretch and possible idea for the demo) - Vamshi
    1. NFO demo through SMO
    2. https://drive.google.com/drive/folders/1kWhqy219L2kebXfBf2Q9lUyY2pkXDiyp 
  4. Demo on Tacker for DMS ETSi profile. - Thoshi and Tacker Team
    1. FM and PM data 
    2. https://drive.google.com/drive/folders/1H8eISd6CFeI72fl1AsntD3DuTPaufDQW

K release source code, container images and deployment instructions (and status)

K release source code for SMO can be found in the following repositories

The container images for SMO can be found on the Nexus server, where applicable.
The container images for OpenStack Tacker can be found in OpenStack Kolla repository.

The OpenStack Tacker container can be started with the steps in the following documentation.

The installation instructions for SMO can be found in the documentation page here.

Status

The status of the SMO project is tracked using Jira items. For the latest status refer to the items below.





Infrastructure (INF)

Primary Goals: 

K release Feature Scope:  

K release highlights/accomplishments (  ):

Jira: Status of Epics, User Stories, Tasks, and Issues:

Update at  

  • EPICs:

key summary type created updated due assignee reporter priority status resolution
Loading...
Refresh

  • Stories:

key summary type created updated due assignee reporter priority status resolution
Loading...
Refresh

  •  Tasks:

key summary type created updated due assignee reporter priority status resolution
Loading...
Refresh

  •  Bugs:

key summary type created updated due assignee reporter priority status resolution
Loading...
Refresh

Test status:

Code coverage:

Release Note: TODO

K release source code, images and deployment instructions

  • Each repository has a branch named "j-release" that can be accessed using git: TODO
  • Images for INF project: TODO
  • Deployment instruction: TODO


Integration and Test (INT)

Primary Goals: 

K Feature Scope / Achievements:

K release highlights/accomplishments:

K release source code, container images and deployment instructions


AIML Framework (AIMLFW)

Primary Goals: 

K release highlights/accomplishments:

  •  

EPICs considered for J-release:

Wiki: AI/ML Framework

Tasks / Backlog / JIRA:  https://jira.o-ran-sc.org/projects/AIMLFW/issues

Gerrit / Code:

Sonar / Test Coverage Reports:

Documentation:

https://docs.o-ran-sc.org/en/latest/projects.html#ai-ml-framework

Installation/Demo guides:

AIMLFW: https://docs.o-ran-sc.org/projects/o-ran-sc-aiml-fw-aimlfw-dep/en/latest/installation-guide.html

Demo videos:

Files for K release

Release Container images:

O-RAN specification References:


Documentation (DOC)

Primary Goals: publish J release document

K release Feature Scope: publish J release document

PTL: Weichen Ni 

K release highlights/accomplishments ():

publish K release document:https://docs.o-ran-sc.org/en/latest/

Release Note:


K release source code, images and deployment instructions

N/A