- Anomaly Detection Use Case
- Components
- A1 Mediator
- Demo1 (a demo xApp maintained by the RICP project)
- E2 Manager (E2M)
- E2 Terminator (E2T)
- Influx-DB Wrapper
- Logging (not tracing)
- O1 mediator
- RIC Alarm System
- RIC Message Router (RMR)
- RNIB
- Routing manager
- Subscription manager
- xApp Framework for CXX (xapp-frame-cpp)
- xApp Framework for Go (xapp-frame)
- xApp Framework for Python (xapp-frame-py)
- Introduction and guides
- Organizational issues
- Overall architecture (not component-specific)
- Recent updates in wiki
- RIC benchmarking
- RIC deployment
- RIC test automation
- Scope of the near-RT RIC platform and its components (summary)
Near-Realtime RAN Intelligent Controller | |
---|---|
PTL | |
Summary | Initial RIC Platform to support xAPPs with limited support for O1, A1, and E2 interfaces. |
Project | For the component list see here: scope |
Weekly Meeting | see Project meetings |
Mailing list and #ricp |
24 Comments
505984452@qq.com
How to deploy the RIC platform? I can not find any doc or deploy script.
I download some projects according Scope of the near-RT RIC platform and its components (summary), i need to install every projects?
Thoralf Czichy
We're working on good instructions. For now the best is to start reading README.md in the repo "it/dep" (https://gerrit.o-ran-sc.org/r/gitweb?p=it/dep.git;a=tree). This is maintained outside of the RIC platform project, though. Eventually, we will have the RIC platform deployment in ric-plt/ric-dep.
505984452@qq.com
Recently I have try to deploy RIC platform with "it/dep". I found the deploy environment needs Docker、Kubernetes and Helm. So is there a version limit about docker、k8s and Helm ? Furthermore,can the platform be deployed on a virtual machine?
wangchangjun
Hi Thoralf:
Recently I installed release Amber but failed, Can you help me?
This is the result:
Infact deployment-ricplt-rtmgr-5c5998d788-xv8px is not working. I changed the Command to make this pod running.
I entered the docker container, and ran the script like this:
It seems that the rtmgr can't connect to xApp manager.
My questions is :
Q1: Does the Amber Release contain the xApp Manager? Should I install it myself?
According to the page(https://docs.o-ran-sc.org/projects/o-ran-sc-ric-plt-rtmgr/en/latest/developer-guide.html#installing-routing-manager), I tried to install the mocked xApp manager but failed.
Q2:The state of part pods in Ric-aux are not running, any clue?
Q3:How can I confirm whether the three parts work well or not?
Any help is helpful!
Thanks
Changjun
Saumya Nayak
Hi Everyone,
I'm facing installation issues, while trying to install RIC Amber Release on Two openstack instance One for RIC Platform and other one is for Auxiliary.
Steps :
1. Create Openstack instance.
git clone https://gerrit.o-ran-sc.org/r/it/dep
2. deploy kubernetes infra
3. Deploy RIC Infra.
~/dep# bin/deploy-ric-infra RECIPE_EXAMPLE/RIC_INFRA_RECIPE_EXAMPLE
Modified RIC_INFRA_RECIPE_EXAMPLE by changing the helm repository IP with the openstack allocated IP.
#helmRepository: "http://10.0.2.100:32080/helm"
helmRepository: "http://172.25.136.86:32080/helm"
Got error for these two pods.
ricinfra deployment-tiller-ricxapp-65f9cbc8d7-fgpnx 0/1 ContainerCreating 0 21s
ricinfra tiller-secret-generator-5kzgk 0/1 ImagePullBackOff 0 21s
Even though Repositories path and credentials are available.
kubectl describe po tiller-secret-generator-5kzgk -n ricinfra
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Scheduled <unknown> default-scheduler Successfully assigned ricinfra/tiller-secret-generator-5kzgk to ric-installation
Normal Pulling 6m26s (x4 over 7m54s) kubelet, ric-installation Pulling image "nexus3.o-ran-sc.org:10004/o-ran-sc/it-dep-secret:0.0.2"
Warning Failed 6m23s (x4 over 7m51s) kubelet, ric-installation Failed to pull image "nexus3.o-ran-sc.org:10004/o-ran-sc/it-dep-secret:0.0.2": rpc error: code = Unknown desc = Error response from daemon: manifest for nexus3.o-ran-sc.org:10004/o-ran-sc/it-dep-secret:0.0.2 not found
Warning Failed 6m23s (x4 over 7m51s) kubelet, ric-installation Error: ErrImagePull
Warning Failed 5m57s (x6 over 7m51s) kubelet, ric-installation Error: ImagePullBackOff
Normal BackOff 2m52s (x19 over 7m51s) kubelet, ric-installation Back-off pulling image "nexus3.o-ran-sc.org:10004/o-ran-sc/it-dep-secret:0.0.2"
It would be very helpful if someone can provide installation instructions.
wangchangjun
Hi Saumya:
I am also trying to install Amber and also failed.
If you want to install Amber, I think you should download the Amber branch by:
git clone https://gerrit.o-ran-sc.org/r/it/dep -b Amber
And you should download the lacking docker images yourself and import to your environment.
Thanks
Changjun
Lusheng Ji
Thanks Changjun.
Yes that is correct. Please clone the Amber branch.
We have two docker image repos, one at nexus3.o-ran-sc.org:10002 and the other at nexus3.o-ran-sc.org:10004. 10004 is a "staging" repo and images on it will expired in 30 days and removed. 10002 is a "release" repo and images on it will not expire.
Helm charts and overrides on the Amber branch point to images on the release registry, while Helm charts and overrides on the master branch point to images on the staging registry,
Lusheng
Thoralf Czichy
These kind of questions are better handled by a post to the O-RAN-SC mailing list: main@lists.o-ran-sc.org also including the tag #RICP into the subject of the message. It's rare that comments on this wiki are checked.
Please note that the O-RAN SC mailing lists are moderated mailing lists for preventing spams. The first email from any sender needs to be verified manually before forwarded onto the lists. Often this is the reason if you do not see your email showing up. If this happens, please also send a direct email to Lusheng Ji or the PTL (Thoralf Czichy (following the logic of firstname.lastname@nokia.com)) and one of use will help unblocking it.
Neal Wu
Hi Everyone,
I am curious about the difference between this project and Akraino.
As mentioned in the architecture pdf, Akraino had been released and used as the Near-Realtime RIC platform.
bujunuri ramanareddy
Hi Everyone,
I have been trying to install Near-Realtime RIC using oracle-virtual box VMs. but not able to install O-ran on the top of K8s cluster. I have been facing some issue like pods are not in the running state. Could any please help me in this regards? Thanks in advance.
Could anyone post the steps to install O-RAN on Virtualbox Vms/Openstack VMs?
Bujunuri Reddy
Hi Everyone,
when installing Near RealTime RIC on Oracle-Virtualbox VMs, Core-dns pods are in the "Crealoopbackoff "status while remaining pods are in the running state.
Could anyone please give the suggestion on the issue above?
when sending mails main@lists.o-ran-sc.org , Mails are not getting delivered. To get reply from the community, to whom i need to send mail. Any suggestions?
Bujunuri Reddy
Hi Team,
while installing the RIC-Aux cluster as
part of The installation of RIC on Openstack VMs.
One pod for Ric-dashboard is in the state of ImagePullBackOff.
when I checked for that image in the nexus repo, There is an image with different tags but not the one which Docker is trying to pull.
Could anyone help me out on this Please? or keep that image in the Repo?
HIBATUL AZIZI BIN HISYAM NG
hi team
I have the same issue as Bujunuri Reddy. any update or solution for this?
Nagachetan Km
Hi HIBATUL AZIZI BIN HISYAM NG,
I too faced the same issue and got the image id changed to 2.1.0 and it worked, i guess there was typo happened. You can try using the
sudo docker pull nexus3.o-ran-sc.org:10004/o-ran-sc/ric-dashboard:2.1.0 and also update in your k8s template and then try the deployment.
Thanks,
Naga Chetan
Argon Cheng
Hello team,
May I know if current RIC could work with LTE eNodeb or not?
Thanks!
Anh Trung Le Nguyen
Hi all,
Could you let me know the purpose of AUX cluster?
Thanks,
Trung.
Irene Velasco
Hi all,
The recipe for installing the RIC platform uses Helm v2.12.3 which is deprecated. Any plans to updating it to use Helm v3? They have also moved out from storage.google.apis.com so anything pointing there will respond with 403 forbidden.
I have tried changing the route to the one in github (get.helm.sh) but looks like the v2.12.3 itself still uses the google storage, so it fails.
+ helm init -c
Creating /root/.helm
Creating /root/.helm/repository
Creating /root/.helm/repository/cache
Creating /root/.helm/repository/local
Creating /root/.helm/plugins
Creating /root/.helm/starters
Creating /root/.helm/cache/archive
Creating /root/.helm/repository/repositories.yaml
Adding stable repo with URL: https://kubernetes-charts.storage.googleapis.com
Error: Looks like "https://kubernetes-charts.storage.googleapis.com" is not a valid chart repository or cannot be reached: Failed to fetch https://kubernetes-charts.storage.googleapis.com/index.yaml : 403 Forbidden
Thanks!
Irene Velasco
I solved this installing Helm v2.17.0 instead of v2.12.3.
Thanks
Thoralf Czichy
This is indeed the workaround that I was using as well, but there's also this commit that changed it to 2.17.0 in Jun 2021 https://gerrit.o-ran-sc.org/r/gitweb?p=it/dep.git;a=commit;h=ff04eeabb5f77c060710a916270ed3eea064d1d1 in the master branch. Did you use the master branch of it/dep?
Ftmzhra Safaeipour
Hi,
Thank you for the complete guide.
I intended to add the nearRT-RIC to the O1. I have the nearRT-RIC project successfully installed and running. In the O1 project, the tests were completed successfully (according to this page: https://wiki.o-ran-sc.org/pages/viewpage.action?pageId=35881895)
When I am attempting to add the nearRT-RIC to the O1 via the command below, the nearRT-RIC stays in the "connecting" mode.
curl -u admin:Kp8bJ4SXszM0WXlhak3eHlcse2gAw84vaoGGmJvUy2U -X POST "http://<HOST_IP>:8181/rests/operations/netconf-node-topology:create-device" -H "accept: */*" -H "Content-Type: application/json" -d '{"input":{"pass-through":{},"login-password":{"username":"netconf","password":"netconf!"},"host":"'"$HOST_IP"'","port":"18310","node-id":"nearRtRIC"}}')
I am not sure how to specify the HOST_IP and port variables in this command.
I have attached the list of nearRT-RIC pods.
Thank you
Rajesh Kumar
Hi usually IP address is your Node or VM IP and port is your O1 mediator netconf port . to get port in your k8s cluster use " kubectl get svc -n ricplt | grep netconf". also you might need to change password to 'netconf' in curl command.
Ftmzhra Safaeipour
Hi Rajesh Kumar,
Thank you for your response.
I updated the port number and the password, and this is the result.
When I use the "curl" command, I get 204 status code for adding the nearRT-RIC and 200 for checking the connection. Yet, in the GUI, the connection status is "connecting", and it also keeps showing the below message; Updating network element [$name].
Thank you.
Francisco Javier Curieses Sanz
hi Ftmzhra Safaeipour,
Viewing your image, I can view that you have du_sim and ru_sim connected to the RIC, is that true?
I would like to know what du_sim and ru_sim you have deployed.
I have RIC (non and near RT) deployed in two virtual machine, but I want to test with CU/DU/RU simulator.
Also, what is the tool that you are using to manage the newworks elements?
Thanks in advance.
BR,
Fran
Vineet Aggarwal
Hi, does anyone know how to install near-RT RIC platform on redhat or centos machine ?