Pre-requisites

Following are the pre-requisites you must have before proceeding with the Cloud Native User Data Repository installation.

Oracle Communications User Data Repository Software

The Oracle Communications User Data Repository software consists of:

Oracle Communications User Data Repository Helm Chart - It reflects the Oracle Communications User Data Repository software version. It comes in form of a zipped tar file.
Software images of the micro-services. They come in form of docker images and/or tar file.

The following software must be installed.

Software	Version
Kubernetes	v1.13.3
HELM	v2.12.3

Additional software that needs to be deployed as per the requirement of the services:

Software	Version	Notes
elasticsearch	1.21.1	Needed for Logging Area
elastic-curator	1.2.1	Needed for Logging Area
elastic-exporter	1.1.2	Needed for Logging Area
logs	2.0.7	Needed for Logging Area
kibana	1.5.2	Needed for Logging Area
grafana	2.2.0	Needed for Metrics Area
prometheus	8.8.0	Needed for Metrics Area
prometheus-node-exporter	1.3.0	Needed for Metrics Area
metallb	0.8.4	Needed for External IP
metrics-server	2.4.0	Needed for Metric Server
tracer	0.8.3	Needed for Tracing Area

Note:

In case any of the above services are needed and the respective software is not installed in CNE, install software before proceeding.

Note:

Some of the above mentioned softwares are updated frequently. Later versions than those listed above should work with UDR 1.3. Some UDR features and services behave or work differently depending on the software being used.

Create Database User/Group

The UDR uses a NDB MySQL database to store the subscriber information.

The UDR deployment using MySQL NDB cluster requires the database administrator to create user in MYSQL DB and to provide the user with necessary permissions to access the tables in the NDB cluster.

Login to the server where the ssh keys are stored and SQL nodes are accessible.
Connect to the SQL nodes.
Login to the Database as a root user.

Create a user and assign it to a group having necessary permission to access the tables on all the SQL nodes:

CREATE USER '<username>'@'%' IDENTIFIED BY
'<password>';
DROP DATABASE if exists udrdb;
CREATE DATABASE udrdb CHARACTER SET utf8;
GRANT SELECT, INSERT, CREATE, ALTER, DROP, LOCK TABLES, CREATE
TEMPORARY TABLES, DELETE, UPDATE,EXECUTE ON udrdb.* TO
'<user>'@'%';
USE <db_name>;

Network access

The Kubernetes cluster hosts must have network access to:

quay.io/datawire/ambassador docker image repository
Local docker image repository where the Oracle Communications User Data Repository images are available
Local helm repository where the Oracle Communications User Data Repository helm charts are available

Laptop/Desktop Client software

Following are the requirements for the laptop/desktop where the deployment commands shall be executed:

Network access to the helm repository and docker image repository
Helm repository must be configured on the client
Network access to the Kubernetes cluster
Necessary environment settings to run the kubectl commands. The environment should have privileges to create namespace in the Kubernetes cluster.
Helm client installed with the push plugin. The environment should be configured so that the 'helm install' command deploys the software in the Kubernetes cluster.

Note:

All the kubectl and helm related commands that are used in this document must be executed on a system depending on the infrastructure of the deployment. It could be user machine such as VM, server, local desktop and so on.