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

Compare with Current View Page History

« Previous Version 30 Next »

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:

Deploy Nonrtric
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:

Undeploy Nonrtric
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:

Get Pods
>sudo kubectl -n nonrtric get pod 

NAME                                   READY   STATUS    RESTARTS   AGE
a1-sim-osc-0                           1/1     Running   0          61m
a1-sim-osc-1                           1/1     Running   0          51m
a1-sim-std-0                           1/1     Running   0          61m
a1-sim-std-1                           1/1     Running   0          51m
a1-sim-std2-0                          1/1     Running   0          61m
a1-sim-std2-1                          1/1     Running   0          51m
a1controller-64c5b7fc56-rkmx2          1/1     Running   0          61m
controlpanel-6fb697f949-rrvnq          1/1     Running   0          61m
db-76d79cd769-q84pc                    1/1     Running   0          61m
dmaapadapterservice-0                  1/1     Running   0          61m
dmaapmediatorservice-0                 1/1     Running   6          61m
helmmanager-0                          1/1     Running   0          61m
informationservice-0                   1/1     Running   0          61m
nonrtricgateway-8c87c678d-8nl82        1/1     Running   0          61m
policymanagementservice-0              1/1     Running   0          61m
rappcatalogueservice-f77f47cb9-85hjq   1/1     Running   0          61m
  • No labels