O-RAN notes(10)---Bronze nonrtric/ricplt IoT using A1 for Policy Management(1)

Refer to links: https://wiki.o-ran-sc.org/display/GS/Running+A1+and+O1+Use+Case+Flows

There are two ways for Policy management, either from nonrtric or from ricplt(aka, Near-RT RIC):

I will introduce several topics in following posts:

(1) HOW-TO: connect nonrtric to ricplt(aka, Near-RT RIC)

(2) HOW-TO: manage Policy using nonrtric-controlpanel

(3) HOW-TO: manage Policy using Policy-Agent(aka, the policymanagementservice) 

(4) HOW-TO: manage Policy using A1-Controller

 

First of all, you should have SMO and RICPLT deployed on seperate VMs:

(12:31 dabs@smobronze bin) > ip addr | grep ens33
2: ens33: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    inet 192.168.43.172/24 brd 192.168.43.255 scope global dynamic noprefixroute ens33

smobronze is the SMO VM.

(13:16 dabs@ricpltbronze dep) > ip addr | grep ens33
2: ens33: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    inet 192.168.43.210/24 brd 192.168.43.255 scope global dynamic noprefixroute ens33

ricpltbronze is the RICPLT VM, and its cluster ip is: 192.168.43.210.

 

Let's begin with first topic:

(1) HOW-TO: connect nonrtric to ricplt(aka, Near-RT RIC)

First we need to re-deploy nonrtric.

 

First step, update the example_recipe.yaml of nonrtric to include correct ip/port of the ricplt cluster:

(20:20 dabs@smobronze NONRTRIC) > pwd
/home/dabs/oran/dep/smo/bin/smo-deploy/smo-dep/RECIPE_EXAMPLE/NONRTRIC

(20:20 dabs@smobronze NONRTRIC) > sudo vim example_recipe.yaml 

Note: Since we are going to access ricplt from outside the cluster, we will use the nodePort( =32080). As we can see, kong-proxy of ricplt has nod