You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

These are the planned versions to be used for the E release (E-release status: TODO).

Use the recipe file RECIPE_EXAMPLE/example_recipe_oran_e_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)nexus3.o-ran-sc.org:10002/o-ran-sc/ric-plt-e2mgr:


docker: ric-plt-e2 (E2 termination)nexus3.o-ran-sc.org:10002/o-ran-sc/ric-plt-e2:
docker: ric-plt-submgrnexus3.o-ran-sc.org:10002/o-ran-sc/ric-plt-submgr:
docker: ric-plt-rtmgrnexus3.o-ran-sc.org:10002/o-ran-sc/ric-plt-rtmgr:
docker: ric-plt-a1nexus3.o-ran-sc.org:10002/o-ran-sc/ric-plt-a1:
docker: ric-plt-appmgrnexus3.o-ran-sc.org:10002/o-ran-sc/ric-plt-appmgr:
docker: ric-plt-alarmmanagernexus3.o-ran-sc.org:10002/o-ran-sc/ric-plt-alarmmanager:
docker: jaegeradapterdocker.io/jaegertracing/all-in-one:
docker: ric-plt-o1nexus3.o-ran-sc.org:10002/o-ran-sc/ric-plt-o1:


docker: ric-plt-vespamgrnexus3.o-ran-sc.org:10002/o-ran-sc/ric-plt-vespamgr:
docker: xapp-onboarder (dms_cli)git clone -b dawn "https://gerrit.o-ran-sc.org/r/ric-plt/appmgr"
docker: ric-plt-dbaas (database)

nexus3.o-ran-sc.org:10002/o-ran-sc/ric-plt-dbaas:


docker: influxDB (optional)docker.io/influxdb:1.8.0-alpine
docker: mgxapp (optional metrics gateway xApp)

not planned to be released in D release (See RIC-799)


library; rmrversion ... (XXX-XX-2021)
library: mdclogversion ... (XXX-XX-2021)
library: ricxfcpp (xapp-frame-cpp)version ... (XXX-XX-2021)
library: riclibe2apversion ... (XXX-XX-2021)
library: sdlversion ... (XXX-XX-2021)
library: rnibversion ... (XXX-XX-2021)
module: mdclogpyversion ... (XXX-XX-2021)
module: ricsdl (sdl for python)version ... (XXX-XX-2021)
module xapp-frame-py (in pypi = ricxappframe)version ... (XXX-XX-2021)


End-of-release tasks TODO UPDATE

  1. Complete code upload/update
  2. 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
    1. status 2021-11-17
    2. no actions needed for
    3. ric-plt/a1 85,3 // no bugs (2021-01-26)

    4. ric-plt/alarm-go 0,0 // no bugs (2021-01-31)

    5. ric-plt/appmgr 0,0 // 1 major bug (2021-01-31)

    6. ric-plt/asn1-documents not applicable

    7. ric-plt/dbaas 0,0 // 1 blocker bug in UT code (2021-01-27) - seems not to be anymore in latest version of source code.

    8. ric-plt/e2 0,0 // 2 blocker bugs (2021-06-18) - Thoralf raised RIC-802 and send e-mail to Dhiraj, Subhash and Naman. 2021-08-17: RIC-802 is for subteam-n in E. No other news

    9. ric-plt/e2mgr 88,4 // no bugs (2021-01-30)

    10. ric-plt/lib/rmr 86,1 // no bugs (2021-08-17)

    11. ric-plt/rtmgr 77,8 // no bugs (2021-01-31)

    12. ric-plt/sdl  66,6 // 1 minor vulnerability bug (2021-01-29)

    13. ric-plt/sdlgo 45,5 // no bugs (2021-02-01)

    14. ric-plt/streaming-protobufs 0,0 // no bugs (2021-01-31)

    15. ric-plt/submgr 33,4 // no bugs (2021-01-31)

    16. ric-plt/tracelibcpp 0,0 // 1 major bug (2021-08-10)

    17. ric-plt/tracelibgo 94,7 // no bugs (2021-01-31)

    18. ric-plt/vespamgr 79,0 // no bugs (2020-12-07)

    19. ric-plt/xapp-frame 0,0 // no bugs (2021-01-31)

    20. ric-plt/xapp-frame-cpp 95,6 // still 2 blocker bugs (2021-08-04) - same as before. Anybody willing to work on them?

    21. ric-plt/xapp-frame-py 96,3 // 0 blocker bugs (2021-01-26)

    22. com/golog 80,7 // no bugs (2021-01-31)
    23. com/log 73,5 // 1 blocker bug and 8 minor ones (2021-01-27) - same as before. Need to fix Sonarcube issues (with Java version) first.
    24. com/pylog 33,7 // 11 major and minor bugs (2021-01-26
  3. If applicable, release binary artifact(s) such as docker container image(s), or libraries.
    1. 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.
  4. 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.
  5. 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.
    1. Release Notes must be published to https://docs.o-ran-sc.org/en/latest/
    2. Instructions for setting up documentation folder for repo: https://wiki.o-ran-sc.org/display/DOC/Configure+Repo+for+Documentation
  6. After finishing all the above, branch "e-release" (all lower case with a dash between e and release).
    1. Repo owners (committers) can create branch. 
    2. 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 left panel > "Create New"



  • No labels