Skip to content

SMO and Non‐RT RIC deployment

Jump to bottom
alex-onf edited this page Aug 6, 2024 · 4 revisions

This refers to the j-release-alignment branch!

Prerequisites

These tools must be installed (summary from the README.md):

  • kubernetes

  • helm3

  • bash

  • cmd 'envsubst' must be installed (check by cmd: 'type envsubst' )

  • cmd 'jq' must be installed (check by cmd: 'type jq' )

    • can be installed with sudo apt update and then sudo apt install -y jq

  • keytool

  • openssl

Istio then needs to be installed for k8s. Details here, but in summary:

  • helm repo add istio https://istio-release.storage.googleapis.com/charts
  • helm repo update
  • kubectl create namespace istio-system
  • helm install istio-base istio/base -n istio-system --set defaultRevision=default
  • helm ls -n istio-system
  • helm install istiod istio/istiod -n istio-system --wait
  • helm ls -n istio-system
  • helm status istiod -n istio-system
  • kubectl get deployments -n istio-system --output wide

Deployment

The solution can be then deployed by running ./install-nrt.sh from the install folder. This will deploy the Non-RT RIC components, SMO components and a simulated O-DU network function.

Sometimes, the first VES message that is sent in the system is being lost. This means that the VES pnfRegistration message that the simulated O-DU sends might get lost and we will not see the NETCONF Connection between the SMO (OAM Controller) and the simulated NF established. If that happens, we can redeploy the O-DU, deleting the old instance and creating a new one that would trigger another VES pnfRegistration message.

  • helm uninstall -n ran-o1-sim ran-o1-sim-du
  • helm install --wait --create-namespace -n ran-o1-sim -f helm/global-values.yaml ran-o1-sim-du helm/ran-o1-sim

The OAM controller GUI can then be accessed on NodePort 31766, with username admin and password Kp8bJ4SXszM0WXlhak3eHlcse2gAw84vaoGGmJvUy2U, and under the Connect tab we will see the simulated NF. The VES collector listens on http on NodePort 31760 and on https on NodePort 31761. Credentials for sending a VES message are username sample1 and password sample1.

Clone this wiki locally