This wiki describes how to deploy the NONRTRIC components within Kubernetes cluster.
NONRTRIC Architechture
NONRTRIC composes of four major components,
- Control Panel
- Policy Management Service
- Enrichment Coordinator Service
- Non RT RIC Gateway
- R-App catalogue Service
- NearRT RIC Simulator
- A1 Controller
Refer this page for more details
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-istallation
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:
>sudo kubectl -n nonrtric get pod NAME READY STATUS RESTARTS AGE controlpanel-5cf589fb4-hbf78 0/1 Running 0 16s enrichmentservice-0 0/1 Running 0 16s nonrtricgateway-c76cb9c8-wp5kt 0/1 Running 0 16s policymanagementservice-0 0/1 Running 0 16s