Date   

Re: Bulk replacing committers in com/golog, com/log, com/pylog, ric-plt/jaegeradapter, ric-plt/tracelibgo, ric-plt/tracelibcpp #ricp

Thoralf Czichy
 

I approve.

 

Thoralf

 

From: main@... <main@...> On Behalf Of Thoralf Czichy via lists.o-ran-sc.org
Sent: Thursday, July 2, 2020 3:55 PM
To: main@...; toc@...
Subject: [oran-sc] Bulk replacing committers in com/golog, com/log, com/pylog, ric-plt/jaegeradapter, ric-plt/tracelibgo, ric-plt/tracelibcpp #RICP

 

hi,

 

as per updated committer change process [1] I propose the following bulk committer change for the

existing near-RT RIC platform components.

 

  Project: near-RT RIC

  Repository location: https://gerrit.o-ran-sc.org/r/admin/repos/...

    com/golog, com/log, com/pylog, ric-plt/jaegeradapter, ric-plt/tracelibgo, ric-plt/tracelibcpp

 

IN:  Ranjit Angajala (LF ID = ranjitk)

IN:  W, Abdulwahid (LF ID = wahidw )

OUT: Katri Turunen (LF ID = KatriT)

OUT: Roni Riska (LF ID = riska)

OUT: Heikki Ahola (LF ID = heikahol) (*1)

 

Katri, Roni, and Heikki (all Nokia) are not working on near-RT RIC topics anymore. Ranjit and Abdulwahid (all Nokia)

have been contributors to the near-RT RIC and also have been committers for other near-RT RIC repos (ric-dep

and rtmgr) already.

 

Current committers (all Nokia):

 

  Katri Turunen

  Roni Riska

  Heikki Ahola  (*1)

  Timo Tietavainen  (*2)

 

Regards,

Thoralf

Near-RT RIC PTL

 

[1] Simplified process for committer changes in a repository of an O-RAN-SC subproject

https://wiki.o-ran-sc.org/display/ORAN/How+to+request+committer+changes  

 

(*1) only a committer in com/golog, com/pylog, ric-plt/jaegeradapter, ric-plt/tracelibgo, but not in the other two.

(*2) only a committer in com/log and com/tracelibcpp, but not in the other four.

 

 


Bulk replacing committers in com/golog, com/log, com/pylog, ric-plt/jaegeradapter, ric-plt/tracelibgo, ric-plt/tracelibcpp #ricp

Thoralf Czichy
 

hi,

 

as per updated committer change process [1] I propose the following bulk committer change for the

existing near-RT RIC platform components.

 

  Project: near-RT RIC

  Repository location: https://gerrit.o-ran-sc.org/r/admin/repos/...

    com/golog, com/log, com/pylog, ric-plt/jaegeradapter, ric-plt/tracelibgo, ric-plt/tracelibcpp

 

IN:  Ranjit Angajala (LF ID = ranjitk)

IN:  W, Abdulwahid (LF ID = wahidw )

OUT: Katri Turunen (LF ID = KatriT)

OUT: Roni Riska (LF ID = riska)

OUT: Heikki Ahola (LF ID = heikahol) (*1)

 

Katri, Roni, and Heikki (all Nokia) are not working on near-RT RIC topics anymore. Ranjit and Abdulwahid (all Nokia)

have been contributors to the near-RT RIC and also have been committers for other near-RT RIC repos (ric-dep

and rtmgr) already.

 

Current committers (all Nokia):

 

  Katri Turunen

  Roni Riska

  Heikki Ahola  (*1)

  Timo Tietavainen  (*2)

 

Regards,

Thoralf

Near-RT RIC PTL

 

[1] Simplified process for committer changes in a repository of an O-RAN-SC subproject

https://wiki.o-ran-sc.org/display/ORAN/How+to+request+committer+changes  

 

(*1) only a committer in com/golog, com/pylog, ric-plt/jaegeradapter, ric-plt/tracelibgo, but not in the other two.

(*2) only a committer in com/log and com/tracelibcpp, but not in the other four.

 

 


Upcoming Event: Sprint demo near-RT RIC - Thu, 07/02/2020 9:00am-10:30am #cal-reminder

main@lists.o-ran-sc.org Calendar <main@...>
 

Reminder: Sprint demo near-RT RIC

When: Thursday, 2 July 2020, 9:00am to 10:30am, (GMT-04:00) America/New York

Where:Zoom Bridge 2 ( https://zoom.us/j/6540568082 )

View Event

Organizer: Thoralf Czichy thoralf.czichy@...

Description: This is the sprint demo for the near-RT RIC.

A more detailed agenda can be found here: https://wiki.o-ran-sc.org/display/RICP/Sprint+demos


Upcoming Event: O-RAN SC RSCA Meeting - Thu, 07/02/2020 9:00am-10:00am #cal-reminder

main@lists.o-ran-sc.org Calendar <main@...>
 

Reminder: O-RAN SC RSCA Meeting

When: Thursday, 2 July 2020, 9:00am to 10:00am, (GMT-04:00) America/New York

Where:Zoom 1 bridge: https://zoom.us/j/9644759813

View Event

Organizer: Rittwik Jana (AT&T)

Description:

(Updated to bi-weekly)

Hi,

This is a recurring meeting to discuss the ORAN-SC software requirements for release “A”. We will have two meetings per week, (9-10 PM eastern Tue and 9-10AM eastern Thu). Please try to attend at least one of the meetings to provide feedback. We will review and update the document here. M0 planning and design timelines are detailed below. 


 
Zoom 1 bridge: https://zoom.us/j/9644759813

O-RAN SC Release "A" Calendar

 

Thanks,

Rittwik


Re: #ricp : O-RAN SMO and Radio plane Setup #ricp

Bassam Ballaji
 

Hello Lusheng,

Thanks for reply. Here some observations regarding your answers :

 
  •   Should I deploy the near RT RIC in the same VM as SMO, or in a different ubuntu 18.04 VM ?

[lji] It is designed to run in a separate K8S cluster.  If you have noticed, the versions of K8S for SMO and for Near RT RIC are different.  SMO needs 1.15 (this is really ONAP requirement) and Near RT RIC needs 1.16.  Also in real deployments you will likely have SMO at a central location while Near RT RIC’s in more edge locations.
--> Response is clear and helpful, thanks. I see a functional "reference design" here  https://docs.o-ran-sc.org/en/latest/architecture/architecture.html  , but is there any infrastructure "reference design" with infra components and spec (servers & platform versions) in O-RAN project home ?

 

·  I don't see any reference to the rest of radio plane components (O-CU / O-CU-CP / O-CU-UP / O-DU / O-RU) as installation packages, would you please share the setup procedure page ? And also I need to know if it's possible to setup all these components in the same ubuntu 18.04 VM ?

[lji] O-CU has only seed source code for Bronze release.  It has no artifacts that are integrated in Bronze end-to-end use cases.  O-DU – Near RT RIC interaction is limited to E2connecion set up.  As things currently stand, you would be able to run O-DU HIGH and Near RT RIC on the same VM, but including SMO (more specifically the ONAP components) in the same VM is difficult due to the difference in K8S version.
--> Response still unclear ... O-CU is still under developpement process within BRONZE release ? or it will be removed ? 
--> Also, I don't see O-DU setup package in 
https://wiki.o-ran-sc.org/display/GS/Getting+Started , is it packaged with Near RT RIC or available as a standalone package in different location ?

 

  • Finally, the interfaces : O1, A1, E2 are established by default between components or is there a particular procedure for this ?

[lji] There are setups required for peers finding each other.  Unfortunately this is rather complicated because the ways they are set up are not consistent.  For O1, it is setup by injecting a json config into SDNC runtime; for A1, it is set up in the recipe for the NonRTRIC before NonRTRIC is deployed (or needing redeploy); for E2, it needs to be compiled into the O-DU HIGH runtime.  We have showed some of them in demo videos.  But have not included in instructions yet because we are still in-progress making these steps easier, and trying to automate the setups as much as possible.  So please stay tuned.
--> Response is clear and helpful, thanks. Yes, stay tuned for this purpose :) 


Rgds,
Bassam

 

 

 


Re: OTF deployment related queries #nonrtric

jx088j@...
 

The database deployment instructions have changed recently. Attached is the new deployment instructions. The database should be set up first.

Thanks,

Justin


Re: #ricp : O-RAN SMO and Radio plane Setup #ricp

Lusheng Ji
 

Hi Bassam,

 

Thanks for your interest.  Please see in-line for answers to your questions.

 

Lusheng Ji

AT&T

O-RAN SC INT

 

 

From: <main@...> on behalf of Bassam Ballaji <bassam.ballaji@...>
Reply-To: "main@..." <main@...>
Date: Monday, June 29, 2020 at 9:26 AM
To: "main@..." <main@...>
Subject: [oran-sc] #ricp : O-RAN SMO and Radio plane Setup

 

In regard of your new release BRONZE, I'm following the step-by-step setup process to install all O-RAN components (non RT RIC / real RT RIC / ....) available in the link : https://wiki.o-ran-sc.org/display/GS/Getting+Started 

 

So as a cloud approach :

 

I created an ubuntu 18.04 VM in Azure Cloud subscription where I deployed a Kubernetes platform as of the link : https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/install-kubeadm/ 

 

Then, I deployed the SMO part (non RT RIC) according to the process : https://wiki.o-ran-sc.org/display/GS/SMO+Installation 

 

So now, I'm targeting the radio plane deployment, I started with the Near RT RIC as of the process in this link :  https://wiki.o-ran-sc.org/display/GS/Near+Realtime+RIC+Installation?&#comments

 

But I have several questions :

·  Should I deploy the near RT RIC in the same VM as SMO, or in a different ubuntu 18.04 VM ?

[lji] It is designed to run in a separate K8S cluster.  If you have noticed, the versions of K8S for SMO and for Near RT RIC are different.  SMO needs 1.15 (this is really ONAP requirement) and Near RT RIC needs 1.16.  Also in real deployments you will likely have SMO at a central location while Near RT RIC’s in more edge locations.

·  I don't see any reference to the rest of radio plane components (O-CU / O-CU-CP / O-CU-UP / O-DU / O-RU) as installation packages, would you please share the setup procedure page ? And also I need to know if it's possible to setup all these components in the same ubuntu 18.04 VM ?

[lji] O-CU has only seed source code for Bronze release.  It has no artifacts that are integrated in Bronze end-to-end use cases.  O-DU – Near RT RIC interaction is limited to E2connecion set up.  As things currently stand, you would be able to run O-DU HIGH and Near RT RIC on the same VM, but including SMO (more specifically the ONAP components) in the same VM is difficult due to the difference in K8S version.

Finally, the interfaces : O1, A1, E2 are established by default between components or is there a particular procedure for this ?

[lji] There are setups required for peers finding each other.  Unfortunately this is rather complicated because the ways they are set up are not consistent.  For O1, it is setup by injecting a json config into SDNC runtime; for A1, it is set up in the recipe for the NonRTRIC before NonRTRIC is deployed (or needing redeploy); for E2, it needs to be compiled into the O-DU HIGH runtime.  We have showed some of them in demo videos.  But have not included in instructions yet because we are still in-progress making these steps easier, and trying to automate the setups as much as possible.  So please stay tuned.

 

 

Looking forward to hearing from you,

Regards,


Re: Committer changes in RICAPP repo ric-app/qp-driver (IN: Chris Lott, OUT: Tommy Carpenter)

JACOBSON, GUY J (GUY J)
 

approved

 

From: "HILTUNEN, MATTI (MATTI)" <hiltunen@...>
Date: Monday, June 29, 2020 at 3:34 PM
To: "toc@..." <toc@...>
Cc: "main@..." <main@...>, "LUCAS, JOHN (JACK)" <jflucas@...>, "CARPENTER, TOMMY J" <tc677g@...>, "DANIELS, EDWARD S (EDWARD)" <daniels@...>, "JACOBSON, GUY J (GUY J)" <guy@...>
Subject: Committer changes in RICAPP repo ric-app/qp-driver (IN: Chris Lott, OUT: Tommy Carpenter)

 

Jack, Tommy, Scott, Guy,

 

As per updated committer change process [1] I propose the following committer changes in the existing RICAPP component qp-driver (= ric-app/qp-driver). Please vote by simply replying to this e-mail with "approved" or "not-approved" back to main@... and toc@... . O-RAN-SC TOC is copied as FYI for this approval process. If approved, we do the change in INFO.yaml without further ado.

 

Repository location: https://gerrit.o-ran-sc.org/r/admin/repos/ric-app/qp-driver

Project: RICAPP

 

IN: Chris Lott (LF ID = cl778h)

OUT: Tommy Carpenter

 

Chris is working for AT&T and has been an active committer and contributor for various near-RT RIC and RICAPP components already. Tommy has moved to other activities.

 

Current committers:  

Jack Lucas

Tommy Carpenter

Scott Daniels

Guy Jacobson

Matti Hiltunen (PTL)

 

Matti

 

[1] Simplified process for committer changes in a repository of an O-RAN-SC subproject https://wiki.o-ran-sc.org/display/ORAN/How+to+request+committer+changes 


OTF deployment related queries #nonrtric

sangeetha-kr@...
 

Hi,
  I have referred below installation document guide for deploying OTF in my lab and got few doubts on this deployment part to proceed. 

 

 

 

https://docs.o-ran-sc.org/projects/o-ran-sc-it-otf/en/latest/developer-guide.html

  

Below are the points :

 

1. From this git repository I am able to see OTF deployment in 3 ways , one using helm charts, another in docker and third one is yaml.

I have tried docker way and successfully deployed OTF frontend, OTF service api and Camunda. All 3 came up but Service API and Camunda stopped after running for 1min.

Kindly guide me in which way you have stood up OTF and comment on this service api, camunda for exit status.

 

OTF git hub:

https://gerrit.o-ran-sc.org/r/gitweb?p=it/otf.git;a=summary

 

commands used to deploy:

 

docker run -itd --name otffrontend --privileged -e OTF_URL='http://192.168.122.243:8082/' -p 8082:32524 --network='host' otf-frontend:0.0.1-SNAPSHOT

docker run -d --network="host" otf-service-api:0.0.1-SNAPSHOT

docker run -d --network="host"otf-camunda:0.0.1-SNAPSHOT

 

 

root@master:~# docker ps -a | grep otf

8c448241ac2a        otf-service-api:0.0.1-SNAPSHOT                "java -jar app.jar"      37 seconds ago      Up 35 seconds                                         admiring_fermi

10cbfa833782        otf-frontend:0.0.1-SNAPSHOT                   "npm start"              5 hours ago         Up 5 hours                  0.0.0.0:8082->32524/tcp   otffrontend

9cda7a44edca        otf-camunda:0.0.1-SNAPSHOT                    "java -jar app.jar"      3 days ago          Exited (1) 3 days ago                                 otfcamunda

 

root@master:~# docker ps -a | grep otf

8c448241ac2a        otf-service-api:0.0.1-SNAPSHOT                "java -jar app.jar"      52 seconds ago      Exited (1) 13 seconds ago                                     admiring_fermi

10cbfa833782        otf-frontend:0.0.1-SNAPSHOT                   "npm start"              5 hours ago         Up 5 hours                          0.0.0.0:8082->32524/tcp   otffrontend

9cda7a44edca        otf-camunda:0.0.1-SNAPSHOT                    "java -jar app.jar"      3 days ago          Exited (1) 3 days ago                                         otfcamunda

  

2. Under OTF database I have seen installdbs.sh file to run but i did not find this file available in the git repository.

Kindly help me the steps to follow up for installing the database.

 

run sudo installdbs.sh and export PATH=/usr/local/mysql/bin:$PATH to add mysql commands to path

run sudo createMongoUser.sh

edit mongo to create a replica set by modifying replication and net fields on file /etc/mongod.conf

add security: authorization: ‘enabled’

after script is ran mysql should be able to be used, connect to mysql using the password set by script and mysql command and

alter the root password

alter user ‘root’@’localhost’ identified by ‘new_password’

grant root ability to connect remotely

grant all on . to ‘root’@’%’ identified by ‘password’

create db and exit mysql shell

create database ‘new_db’

create tables using mysql scripts

mysql -u root -p db < engine.sql

 

 

3. After deploying this OTF frontend docker, UI part of it is not working when i tried to open, but ports are in listening state.

Guide me how to view this UI part of OTF.

 

root@master:~#  lsof -i -P -n | grep 8082

docker-pr 13763            root    4u  IPv6 307767967      0t0  TCP *:8082 (LISTEN)

root@master:~#

 
Please help suggesting the solution for resolving above queries to proceed further.

Thanks & Regards,

Sangeetha.

 

 

 


Upcoming Event: O-RAN SC Integration and Testing Weekly call - Wed, 07/01/2020 9:00am-10:00am #cal-reminder

main@lists.o-ran-sc.org Calendar <main@...>
 

Reminder: O-RAN SC Integration and Testing Weekly call

When: Wednesday, 1 July 2020, 9:00am to 10:00am, (GMT-04:00) America/New York

Where:Zoom 2 bridge: https://zoom.us/j/6540568082

View Event

Organizer: Lusheng Ji lji@...

Description: Hello.  Starting from the week of 08/12, we will hold Integration and Testing Weekly meetings, on every Wednesday after the ToC meeting.  We will use the same bridge as the ToC meeting (Zoom 2 bridge: https://zoom.us/j/6540568082).  Thanks!  Lusheng

 


O-RAN SC TOC Committee - Wed, 07/01/2020 #cal-notice

main@lists.o-ran-sc.org Calendar <noreply@...>
 

O-RAN SC TOC Committee

When:
Wednesday, 1 July 2020
8:00am to 10:00am
(GMT-04:00) America/New York

Where:
Zoom 2 bridge: https://zoom.us/j/6540568082

Description:


Upcoming Event: O-RAN SC TOC Committee - Wed, 07/01/2020 8:00am-10:00am #cal-reminder

main@lists.o-ran-sc.org Calendar <main@...>
 

Reminder: O-RAN SC TOC Committee

When: Wednesday, 1 July 2020, 8:00am to 10:00am, (GMT-04:00) America/New York

Where:Zoom 2 bridge: https://zoom.us/j/6540568082

View Event

Description:


Upcoming Event: Sprint demo near-RT RIC - Thu, 07/02/2020 9:00am-10:30am #cal-reminder

main@lists.o-ran-sc.org Calendar <main@...>
 

Reminder: Sprint demo near-RT RIC

When: Thursday, 2 July 2020, 9:00am to 10:30am, (GMT-04:00) America/New York

Where:Zoom Bridge 2 ( https://zoom.us/j/6540568082 )

View Event

Organizer: Thoralf Czichy thoralf.czichy@...

Description: This is the sprint demo for the near-RT RIC.

A more detailed agenda can be found here: https://wiki.o-ran-sc.org/display/RICP/Sprint+demos


Upcoming Event: O-RAN SC Integration and Testing Weekly call - Wed, 07/01/2020 9:00am-10:00am #cal-reminder

main@lists.o-ran-sc.org Calendar <main@...>
 

Reminder: O-RAN SC Integration and Testing Weekly call

When: Wednesday, 1 July 2020, 9:00am to 10:00am, (GMT-04:00) America/New York

Where:Zoom 2 bridge: https://zoom.us/j/6540568082

View Event

Organizer: Lusheng Ji lji@...

Description: Hello.  Starting from the week of 08/12, we will hold Integration and Testing Weekly meetings, on every Wednesday after the ToC meeting.  We will use the same bridge as the ToC meeting (Zoom 2 bridge: https://zoom.us/j/6540568082).  Thanks!  Lusheng

 


Re: Committer changes in RICAPP repo ric-app/qp-driver (IN: Chris Lott, OUT: Tommy Carpenter)

Scott
 

Approved.

--
E. Scott Daniels
PMTS - AT&T Labs -- Research


Re: Committer changes in RICAPP repo ric-app/qp-driver (IN: Chris Lott, OUT: Tommy Carpenter)

LUCAS, JOHN (JACK) <jflucas@...>
 

approved

 

From: HILTUNEN, MATTI (MATTI)
Sent: Monday, June 29, 2020 3:35 PM
To: toc@...
Cc: main@...; LUCAS, JOHN (JACK) <jflucas@...>; CARPENTER, TOMMY J <tc677g@...>; DANIELS, EDWARD S (EDWARD) <daniels@...>; JACOBSON, GUY J (GUY J) <guy@...>
Subject: Committer changes in RICAPP repo ric-app/qp-driver (IN: Chris Lott, OUT: Tommy Carpenter)

 

Jack, Tommy, Scott, Guy,

 

As per updated committer change process [1] I propose the following committer changes in the existing RICAPP component qp-driver (= ric-app/qp-driver). Please vote by simply replying to this e-mail with "approved" or "not-approved" back to main@... and toc@... . O-RAN-SC TOC is copied as FYI for this approval process. If approved, we do the change in INFO.yaml without further ado.

 

Repository location: https://gerrit.o-ran-sc.org/r/admin/repos/ric-app/qp-driver

Project: RICAPP

 

IN: Chris Lott (LF ID = cl778h)

OUT: Tommy Carpenter

 

Chris is working for AT&T and has been an active committer and contributor for various near-RT RIC and RICAPP components already. Tommy has moved to other activities.

 

Current committers:  

Jack Lucas

Tommy Carpenter

Scott Daniels

Guy Jacobson

Matti Hiltunen (PTL)

 

Matti

 

[1] Simplified process for committer changes in a repository of an O-RAN-SC subproject https://wiki.o-ran-sc.org/display/ORAN/How+to+request+committer+changes 


Committer changes in RICAPP repo ric-app/qp-driver (IN: Chris Lott, OUT: Tommy Carpenter)

HILTUNEN, MATTI (MATTI)
 

Jack, Tommy, Scott, Guy,

As per updated committer change process [1] I propose the following committer changes in the existing RICAPP component qp-driver (= ric-app/qp-driver). Please vote by simply replying to this e-mail with "approved" or "not-approved" back to main@... and toc@... . O-RAN-SC TOC is copied as FYI for this approval process. If approved, we do the change in INFO.yaml without further ado.

Repository location: https://gerrit.o-ran-sc.org/r/admin/repos/ric-app/qp-driver
Project: RICAPP

IN: Chris Lott (LF ID = cl778h)
OUT: Tommy Carpenter

Chris is working for AT&T and has been an active committer and contributor for various near-RT RIC and RICAPP components already. Tommy has moved to other activities.

Current committers:  
Jack Lucas
Tommy Carpenter
Scott Daniels
Guy Jacobson
Matti Hiltunen (PTL)

Matti

[1] Simplified process for committer changes in a repository of an O-RAN-SC subproject https://wiki.o-ran-sc.org/display/ORAN/How+to+request+committer+changes 


Event: OSC: NONRTRIC / OAM / SIM - Joint weekly community SCRUM meeting (Cherry Release) #cal-invite

main@lists.o-ran-sc.org Calendar <main@...>
 

OSC: NONRTRIC / OAM / SIM - Joint weekly community SCRUM meeting (Cherry Release)

When:
Monday, 29 June 2020
1:00pm to 2:00pm
(UTC+00:00) UTC
Repeats: Weekly on Monday, through Monday, 21 December 2020

Where:
https://zoom.us/j/436210993

Organizer: John Keeney John.Keeney@...

Description:
https://zoom.us/j/436210993

Weekly community SCRUM meeting for OSC project: OAM, NONRTRIC, SIM

NONRTRIC: https://wiki.o-ran-sc.org/display/RICNR/Meetings
OAM: https://wiki.o-ran-sc.org/display/OAM/Meeting+notes
SIM: https://wiki.o-ran-sc.org/display/SIM/SIM

Note about daylight savings time

  • Please note that the weekly OAM/NONRTRIC scrum team meeting will continue on Monday’s at 13:00 UTC.
  • During the "Daylight Savings Time" changeover periods (US vs Europe vs Asia) the time of this meeting may fluctuate. Please keep a close eye on the calendar!
  • Summer Daylight Savings time eventually stabilizes to:
    • 6am PDT | 9am EDT | 13:00 UTC | 14:00 BST | 15:00 CEST | 16:00 EEST | 18:30 IST | 21:00 CST | 22:00 JST


#ricp : O-RAN SMO and Radio plane Setup #ricp

Bassam Ballaji
 

In regard of your new release BRONZE, I'm following the step-by-step setup process to install all O-RAN components (non RT RIC / real RT RIC / ....) available in the link : https://wiki.o-ran-sc.org/display/GS/Getting+Started 
 
So as a cloud approach :
 
I created an ubuntu 18.04 VM in Azure Cloud subscription where I deployed a Kubernetes platform as of the link : https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/install-kubeadm/ 
 
Then, I deployed the SMO part (non RT RIC) according to the process : https://wiki.o-ran-sc.org/display/GS/SMO+Installation 
 
So now, I'm targeting the radio plane deployment, I started with the Near RT RIC as of the process in this link :  https://wiki.o-ran-sc.org/display/GS/Near+Realtime+RIC+Installation?&#comments
 
But I have several questions :

  • Should I deploy the near RT RIC in the same VM as SMO, or in a different ubuntu 18.04 VM ?
  • I don't see any reference to the rest of radio plane components (O-CU / O-CU-CP / O-CU-UP / O-DU / O-RU) as installation packages, would you please share the setup procedure page ? And also I need to know if it's possible to setup all these components in the same ubuntu 18.04 VM ?
  • Finally, the interfaces : O1, A1, E2 are established by default between components or is there a particular procedure for this ?
 
Looking forward to hearing from you,
Regards,


Re: Questions regarding DU-Low and DU-High

Zhimin Yuan
 

Hi Alex,
Echo Lusheng, thanks for your interest in O-DU project. please see my in-line responses.

Thanks,
Zhimin

-----Original Message-----
From: main@... <main@...> On Behalf Of Lusheng Ji
Sent: 2020年6月25日 22:23
To: main@...
Subject: Re: [oran-sc] Questions regarding DU-Low and DU-High

Hi Alex,

Thanks for your interest. Please see in-line for responses for two of your questions.

Thanks,
Lusheng

On 6/25/20, 10:14 AM, "main@... on behalf of Alexandru Moise" <main@... on behalf of 00moses.alexander00@...> wrote:

Greetings fellow engineers,

I started posing some technical questions to some of the active o-ran
developers and I was pointed towards this mailing list.

Q1: Does anyone here know if there's a DU-Low demo available anywhere?
I found a DU-High demo that uses a cu_stub and a mac_stub, didn't find a DU-Low
demo as of yet.

[lji] O-DU LOW performed a demonstration for Bronze Sprint 1. You can find the recording here: https://wiki.o-ran-sc.org/display/IAT/Bronze+Dev+Sprint+1+Demonstrations

Q2: Is is possible to run DU-Low in a simulated environment?
[lji] This is best answered by the O-DU LOW team.
[Zhimin] O-DU Low also provide two level test simulator to help L1 testing. We have O-RU test simulator, it’ll help the O-RAN FH interface verification. We have L2 test simulator(testmac) which can be used to bring up L1 for functionality verification and performance dimensioning of L1.

Q3: Is o-ran at a stage yet where DU-High and DU-Low are integrated with eachother?
I started watching some zoom recordings and as of april I think they were not integrated
yet.

[lji] Correct. The O-DU HIGH and LOW integration is targeted to happen at Bronze maintenance release (mid July), for which the two components will communicate with FAPI interface.

Best regards and thank you in advance,
../Alex