Near-RT RIC (K release)
- abdulwahid.w
WORK IN PROGRESS
These are the planned versions to be used for the K-release.
Use the recipe file RECIPE_EXAMPLE/example_recipe_oran_i_release.yaml from ' git clone "https://gerrit.o-ran-sc.org/r/ric-plt/ric-dep" ' to deploy the near-RT RIC platform. This file is aligned with the versions below.
Component (docker image/library/module) | Image in release repo (10002) or in staging repo (10004) | Gerrit review (to be used to recreate image if disappeared from staging) |
docker: ric-plt-e2mgr (E2 manager) | http://nexus3.o-ran-sc.org :10002/o-ran-sc/ric-plt-e2mgr:6.0.6 DONE | Same as J release |
docker: ric-plt-e2 (E2 termination) | http://nexus3.o-ran-sc.org :10002/o-ran-sc/ric-plt-e2:6.0.6 DONE | Same as J release |
docker: ric-plt-submgr | http://nexus3.o-ran-sc.org :10002/o-ran-sc/ric-plt-submgr:0.10.2 DONE | Same as J release |
docker: ric-plt-rtmgr | http://nexus3.o-ran-sc.org :10002/o-ran-sc/ric-plt-rtmgr:0.9.6 DONE | same as I release |
docker: ric-plt-a1 | http://nexus3.o-ran-sc.org :10002/o-ran-sc/ric-plt-a1:3.2.2 DONE | same as I release |
docker: ric-plt-appmgr | http://nexus3.o-ran-sc.org :10002/o-ran-sc/ric-plt-appmgr::0.5.8 DONE |
|
docker: ric-plt-alarmmanager | http://nexus3.o-ran-sc.org :10002/o-ran-sc/ric-plt-alarmmanager:0.5.16 DONE |
|
docker: jaegeradapter | docker.io/jaegertracing/all-in-one:1.12 DONE | no changes. Same version as before from http://docker.io |
docker: ric-plt-o1 | http://nexus3.o-ran-sc.org :10002/o-ran-sc/ric-plt-o1:0.6.3 DONE |
|
docker: ric-plt-vespamgr | http://nexus3.o-ran-sc.org :10002/o-ran-sc/ric-plt-vespamgr:0.7.5 DONE | same as in E release, no new version |
docker: xapp-onboarder (dms_cli) | git clone -b i-release "https://gerrit.o-ran-sc.org/r/ric-plt/appmgr" |
|
docker: ric-plt-dbaas (database) | http://nexus3.o-ran-sc.org :10002/o-ran-sc/ric-plt-dbaas:0.6.4 DONE |
|
docker: influxDB (optional) | Version as before from http://docker.io . Major upgrade compared to F release | |
docker: mgxapp (optional metrics gateway xApp) | not planned to be released in I release (See RIC-799) DONE |
|
docker: ricdms | http://nexus3.o-ran-sc.org :10002/o-ran-sc/ric-plt-ricdms:2.1.1 DONE |
|
library; rmr | version 4.9.4 (Dec-13-2023) DONE |
|
library: mdclog | version 0.1.4-1 (Aug-25-2021) DONE | same as in E release, now new version |
library: ricxfcpp (xapp-frame-cpp) | version 2.3.10 (Dec-13-2023) DONE |
|
library: riclibe2ap | not planned to be updated to E2APv.2.0 in H release due to lack of time (same as before: version 1.1.0 (Jun-04-2021)) DONE |
|
library: sdl (c++) | version 1.6.0 (Mar-14-2022) (no changes) DONE |
|
library: rnib (c++ (="rnib...deb") and golang), | version 1.2.8 (no changes) DONE |
|
module: mdclogpy | version 1.1.4 (Jun-17-2021) DONE | same as in E,F, G, H release, now new version |
module: ricsdl (sdl for python) | version 3.1.3 (no changes) DONE |
|
module xapp-frame-py (in pypi = ricxappframe) | version 3.2.3 (Dec-13-2023) |
|
module xapp-frame (go) | version v0.9.19 (Dec-13-2023) DONE |
|
module xapp-frame-rust (rust) | git clone -b i-release "https://gerrit.o-ran-sc.org/r/ric-plt/xapp-frame-rust" |
|
module sdlgo (go) | version 0.10.4 (Dec-13-2023) DONE |
|
End-of-release tasks
Complete code upload/update
e.g. update the dockerfile to use the latest RMR library: 4.9.4
Double-check from Code coverage reports (click on "primary link" in that page) that all blocker code smells have been addressed as per RC-5 in Release criteria checklist template
status 2023-12-14: no further actions needed
If applicable, release binary artifact(s) such as docker container image(s), or libraries.
Formal instructions: O-RAN Developer's Guide to CI Resources and Processes at the LF. For container image releases we do check "container-tag.yaml" in the repo and from there you get the latest version of the container (the expectation is that during development that version is updated as changes are made to the repo). If it’s the same as in the previous release (Cherry) because there were no changes, or because developers forgot to update that one, update it as well. This has to be committed and merged first. As a second step take the version from container-tag.yaml and update that into .../releases/container-release-ric-plt-e2mgr.yaml (in two places; in row "version" (skip this if the italics text above applied) and in row container_release_tag) also take the commit Id that is the latest and update that into /releases/container-release-ric-plt-e2mgr.yaml. The bold part obviously differs per component.
Update references to artifacts in the above table. Also fill in the last column with reference to the gerrit review that can be used to regenerate the artifact.
Update release notes: Make sure you have a release summary as per RC-1 in Release criteria checklist template: "every component must update their rst release notes (in the doc subfolder in the repo)". Based on this per-component description, the PTL will create a release summary.
Release Notes must be published to Welcome to O-RAN SC K Release Documentation Home — oran master documentation
Instructions for setting up documentation folder for repo: https://lf-o-ran-sc.atlassian.net/wiki/display/DOC/Configure+Repo+for+Documentation
After finishing all the above, branch "i-release" (all lower case with a dash between f and release).
Repo owners (committers) can create branch.
There are several ways to create branch. For example do this: Login to web UI https://gerrit.o-ran-sc.org/r/admin/repos > Find repo, click on repo name > "Branches" in right panel > "Create New"