O-RAN notes(6)---Bronze Near-Realtime RIC(ricplt) deployment (3)//xApp Deployment

First, pull all xApp images manually. There are four xApps for now: 

• Hello World xApp
• QP(QoE Predictor) xApp
• QP Driver xApp
• TS(Traffic Steering) xApp

#docker_pull_xapp.sh
echo && echo Pulling nexus3.o-ran-sc.org:10002/o-ran-sc/ric-app-hw:1.0.6
docker pull nexus3.o-ran-sc.org:10002/o-ran-sc/ric-app-hw:1.0.6

echo && echo Pulling nexus3.o-ran-sc.org:10002/o-ran-sc/ric-app-qp:0.0.2
docker pull nexus3.o-ran-sc.org:10002/o-ran-sc/ric-app-qp:0.0.2

echo && echo Pulling nexus3.o-ran-sc.org:10002/o-ran-sc/ric-app-qp-driver:1.0.9
docker pull nexus3.o-ran-sc.org:10002/o-ran-sc/ric-app-qp-driver:1.0.9

echo && echo Pulling nexus3.o-ran-sc.org:10002/o-ran-sc/ric-app-ts:1.0.11
docker pull nexus3.o-ran-sc.org:10002/o-ran-sc/ric-app-ts:1.0.11

Check that TCP port 32080 is supposed to be listened by service 'r4-infrastructure-kong-proxy': 

(11:49 dabs@ricpltbronze dep) > sudo kubectl get service -A | grep 32080
ricplt        r4-infrastructure-kong-proxy                NodePort    10.99.129.214    <none>        32080:32080/TCP,32443:32443/TCP   13h

However, TCP port 32080 has already been occupied by kube-proxy:

(11:48 dabs@ricpltbronze dep) > sudo netstat -anp | grep 32080
tcp6       0      0 :::32080                :::*                    LISTEN      8675/kube-proxy

There are two solutions to this problem:

(1) change the $(hostname) to the ip addr. of service 'r4-infrastructure-kong-proxy', such as:

#before update
curl --location --request POST "http://$(hostname):32080/onboard/api/v1/onboard/download"  --header 'Content-Type: application/json' --data-binary "@./onboard.hw.url"

#after update
curl --location --request POST "http://10.99.129.214:32080/onboard/api/v1/onboard/download"  --header 'Content-Type: application/json' --data-binary "