This page is

...

This wiki describes how to deploy the NONRTRIC components within Kubernetes cluster.

NONRTRIC Architecture

NONRTRIC comprises several components,

1. Control Panel
2. Policy Management Service
3. Enrichment Coordinator Service
4. Non RT RIC Gateway
5. R-App catalogue Service
6. NearRT RIC Simulator
7. A1 Controller

In the IT/Dep repo, there are helm charts for each these components. In addition, there is a chart called nonrtric, which is a composition of the components above.

Installation

There is a script that packs and installs the components by using the helm command.  The installation uses an values override file, which can be used to customize the  installation.  There is also an example of an override file. This example can be run like this:

sudo dep/bin/deploy-nonrtric dep/nonrtric/RECIPE_EXAMPLE/example_recipe.yaml

The example example_recipe.yaml contains reasonable values and installs a subset of the commands.  The example contains documentation of how the parameters can be set. Most should not be updated,  but for instance the parameters on which components to include should likely be updated.

Un-installation

There is a script that uninstalls installs the NonRT RIC components. It is simply run like this:

sudo dep/bin/undeploy-nonrtric

Introduction to Helm Chart

In NONRTRIC we use Helm chart as a packaging manager for kubernetes. Helm chart helps developer to package, configure & deploy the application and services into kubernetes environment.

For more information you could refer to below links,

https://helm.sh/docs/intro/quickstart/

Namespace

The installation will create one helm release and all created kubernetes objects will be put in a namespace. This name is 'nonrtric' and cannot be changed.

Once the installation is done you can check the created kubernetes objects by using command kubectl. Example:

...

...

out of date.
Please see the relevant page for the latest release: e.g. Release F - Run in Kubernetes