Page History

RIC and SMO Installation completed 

NOTE:  cd to your directory where installation will be, i.e. /home/user

Run ...

$ sudo -i

$ git clone http://gerrit.o-ran-sc.org/r/it/dep

$ cd dep
$ git submodule update --init --recursive --remote

Run ...  For SMO 

$ cd ../etc
$ vi infra.rc   # Review and edit the versions, using the combination for ONAP Frankfurt
$ cd ../bin
$ ./gen-cloud-init.sh   # The stack install script for ONAP will be generated.

completed.

Run ...

$ ./k8s-1node-cloud-init-k_1_16-h_2_12-d_cur.sh

NOTE: Be patient as this takes some time to complete. Upon completion of this script, the VM will be rebooted.  You will then need to login once again.

$ sudo -i

$ kubectl get pods --all-namespaces  # There should be  9 pods running in kube-system namespace.

Run ...

$ cd /home/user/dep/bin
$ ./deploy-ric-platform -f ../RECIPE_EXAMPLE/PLATFORM/example_recipe.yaml
$ kubectl get pods -n ricplt   # There should be ~16 pods running in the ricplt namespace.  

The SMO A1 (policy) flow is almost identical to what we have shown in the xApp (Traffic Steering) flow, with the difference that the policy operations (i.e. policy type creation, policy instance creation) are coming from the SMO instead of directly calling A1 mediator API.

In SMO cluster, the Near RT RIC's coordinates (IP, port, etc) is specified in the recipe for the NonRTRIC.   To check whether SMO has successfully established communication with Near RT RIC,

Run the following on the SMO cluster:

$ curl 

http://$(hostname):

30093/rics

To create a new policy instance under policy type 20008 (Traffic Steering's threshold policy),

Run:

$ POLICY_TYPE_ID="20008"
$ curl -

v i-X PUT --

header "

Content-Type:

 application/json" \
"http://$(hostname):

30091/policy?id=FROMOTF&ric=ric1&service=dummyService&id=${POLICY_TYPE_ID}" \
--data "{\"threshold\" : 1}"