Deploying Cloud Native User Data Repository

The User Data Repository requires a MySQL database to store the configuration and run time data.

The OCUDR Software components as mentioned in pre-requisites section, can be extracted following the below steps.

1. Download ocudr-pkg-1.0.0.0.0.tgz.
2. Untar ocudr-pkg-1.0.0.0.0.tgz.
3. Untar displays the following files:

   ocudr-pkg-1.0.0.0.0.tgz
              |_ _ _ _ _ _ ocudr-1.0.0.tgz (helm chart)
              |_ _ _ _ _ _ ocudr-images-1.0.0.tar (docker images)
              |_ _ _ _ _ _ Readme.txt (Contains cksum and md5sum of tarballs)

4. Check the checksums of tarballs mentioned in the Readme.txt file.
5. After you load the tarballs to docker images, if required, re-tag it according to your specific repository.
   • Run the following command to load the tarball to system.

     # docker load --input /root/ocudr-images-1.0.0.tar

6. If required, user can re-tag the images and push them according to their repo by executing the following command:

   # docker tag ocudr/nudr_datarepository_service:1.0.0 <customer repo>/nudr_datarepository_service:1.0.0
   # docker push <customer repo>/nudr_datarepository_service:1.0.0
   # docker tag ocudr/nrf_client_service:1.0.0 <customer repo>/nrf_client_service:1.0.0
   # docker push <customer repo>/nrf_client_service:1.0.0

Deploying Cloud Native User Data Repository in Kubernetes Cluster

Note:

Before proceeding to helm installation, note that the dbname parameter under MySQL section in ocudr_values.yaml has the default value, udrdb and it is recommended to use the same as the UDR deployment takes the UDR db creation and related table creation and values by connecting to NDBCLUSTER and uses the dbname as udrdb to the do the same.

If user wants to configure a different DB name for UDR DB other than the default value, udrdb, follow the steps mentioned in the section, Modifying UDR DB Name.

To deploy in Kubernetes Cluster:

1. Execute the following command to deploy cloud native User Data repository in Kubernetes Cluster using ocudr_values.yaml file modified as per site configurations.

   helm install <helm chart> [--version <OCUDR version>] --name <release> --namespace <k8s namespace> -f <ocudr_values.yaml>

   In the above command:
   • <helm chart> - is the name of the chart which is of the form <helm repo>/ocudr
   • <OCUDR version> - is the software version (helm chart version) of the User Data Repository. This is optional. If omitted, the default is latest version available in helm repository.
   • <release> - is a name of user's choice to identify the helm deployment
   • <k8s namespace> - is a name of user's choice to identifying the kubernetes namespace of the User Data Repository. All the User Data Repository micro services are deployed in this kubernetes namespace.
   • <ocudr_values.yaml> - is the customized User Data Repository values.yaml file. The OCUDR values.yaml file is a part of customer documentation. Users needs to download the file and modify as per the user site. See Customizing User Data Repository for more details.
2. (Optional) Customize the User Data Repository by overriding the default values of various configurable parameters. See Customizing User Data Repository.
3. Update the following parameters in ocudr_values.yaml file:
   • mysql:
     • primaryhost: "<Primary MYSQL Node of NDB Cluster>"
     • primaryport: "<Port>"
     • secondaryhost: "<Secondary MYSQL Node of NDB Cluster>"
     • secondaryport: "<Port>"
     • dbname: "<DB_name>"
     • dsusername: "<Dbusername>"
     • dspassword: "<Dbpassword>"
   • nrfClient:
     • host:
       • baseurl: "<To connect to NRF for registration>"
       • proxy: "<Proxy setting if any to connect to NRF>"
     • capacityMultiplier: "<Capacity Multiplier>"
     • supirange: "<supi range for UDR>"
     • priority: "<priority>"
     • livenessProbeUrl: "liveness probe url of both nudr-drservice and ocudr ambassador"
     • fqdn: "FQDN of nudr-drservice for NRF to use while sending request. Will be carried in registration request to NRF"