You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

E2 Simulator

...

Description

...


Usage

How to configure E2Sim to initiate the connection towards E2Term(nRT-RIC)


  • Get endpoint of Kong service

MyExample: script

KONG_SVC=$(kubectl get svc -A | grep "kong" | awk '{print $2}')

NODE_PORT=$(kubectl get --namespace ricplt -o jsonpath="{.spec.ports[0].nodePort}" services $KONG_SVC)

NODE_IP=$(kubectl get nodes -o jsonpath="{.items[0].status.addresses[0].address}")

KONG_ADDRESS=${NODE_IP}:${NODE_PORT}

  • Get endpoint of E2Term List from E2Mgr

MyExample: script

NUM_OF_E2T=$(curl -sX GET "http://${KONG_ADDRESS}/e2mgr/v1/e2t/list" -H "accept: application/json" | jq '.')


for id in $(seq 1 ${NUM_OF_E2T}); do

NODE_IP=$(kubectl get pod -n=ricplt -l app=ricplt-e2term-"${id}" -o jsonpath="{.items[0].status.hostIP}")

  NODE_PORT=$(kubectl get svc -n=ricplt service-ricplt-e2term-sctp-"${id}" -o jsonpath="{.spec.ports[0].nodePort}")

  E2T_ADDRESSES[$id]="${NODE_IP}:${NODE_PORT}"

done

MyExample: helm chart

spec:

      containers:

        - name: …..

          image: …..

          imagePullPolicy: …..

          restartPolicy: …..

          command: ["/bin/sh"]

          args: ["-c", ${EXECUTABLE with E2TERM ENDPOINT} ]

…..

  • No labels