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.

Download ocudr-pkg-1.3.0.0.0.tgz.
Untar ocudr-pkg-1.3.0.0.0.tgz.

Untar displays the following files:

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

Check the checksums of tarballs mentioned in the Readme.txt file.
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.3.0.tar
```

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.3.0 <customer repo>/nudr_datarepository_service:1.3.0
# docker push <customer repo>/nudr_datarepository_service:1.3.0
# docker tag ocudr/nrf_client_service:1.3.0 <customer repo>/nrf_client_service:1.3.0
# docker push <customer repo>/nrf_client_service:1.3.0
# docker tag ocudr/nudr_notify_service:1.3.0 <customer repo>/nudr_notify_service:1.3.0
# docker push <customer repo>/nudr_notify_service:1.3.0

Deploying Cloud Native User Data Repository in Kubernetes Cluster

Before deploying the Cloud Native User Data Repository in Kubernetes Cluster, update the following parameters in the ocudr-custom-values-1.3.0.yaml file:

update the following parameters under global section:
mysql:
- dbServiceName : "udrdbservice " #This is a read only parameter. Use the default value.
- port: "<Port>"
- dbname: "<DB_name>"
- dsusername: "<Dbusername>"
- dspassword: "<Dbpassword>"
udrdbservice:
- primaryhost: "<primary sql host>"
- secondaryhost: "<secondary sql host>"
- port: "<Port>"
- targetPort : "<Target Port>"
update the following parameters under nrfclient section:
nrfClient:
- host:
  - baseurl: "<To connect to Network Repository Function (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 nudr-drservice, nudr-notify-service, and ocudr ambassador"
- fqdn: "FQDN of nudr-drservice for NRF to use while sending request. Will be carried in registration request to NRF"

To deploy OCUDR in Kubernetes Cluster:

Execute the following command to deploy cloud native User Data repository in Kubernetes Cluster using the modified ocudr-custom-values-1.3.0.yaml .
```
helm install <helm chart> [--version <OCUDR version>] --name <release> --namespace <k8s namespace> -f <ocudr-custom-values-1.3.0.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. From 1.3.0 release onwards, all pod names, service name, deployment name will be prepended by this release name.
- <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-custom-values-1.3.0.yaml> - is the customized ocudr-custom-values-1.3.0.yaml file. The ocudr-custom-values-1.3.0.yaml file is a part of customer documentation. Users needs to download the file and modify as per the user site.
(Optional) Customize the User Data Repository by overriding the default values of various configurable parameters. See Customizing User Data Repository.