Deploying Cloud Native Unified Data Repository

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

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

Table 2-3 ocudr-custom-values-1.5.0.yaml Parameters

Section Parameter Services
Global mysql:
  • dbServiceName : Default value is "udrdbservice ". This is a read only parameter. Use the default value.
  • port: "<Port>". Default value is 3306
  • dbname: "<DB_name>". Default value is udrdb.
  • dsusername: "<Dbusername>". Default value is udruser
  • dspassword: "<Dbpassword>". Default value is udrpasswd
udrdbservice:
  • primaryhost: "<primary sql host>". Default valus is ocudr-mysql.
  • secondaryhost: "<secondary sql host>". Default value is ocudr-mysql
  • port: "<Port>". Default valus is 3306.
  • targetPort : "<Target Port>". Default value is 3306.
nrfclient nrfclient:
host:
  • baseurl: "<To connect to Network Repository Function (NRF) for registration>". Default URL:
  • proxy: "<Proxy setting if anyone connects to NRF>". Default value is NULL.
  • capacityMultiplier: "<Capacity Multiplier>". Default value is 500.
  • supirange: "<supi range for UDR>". Default value is [{\"start\": \"10000000000\", \"end\": \"20000000000\"}]
  • priority: "<priority>". Default value is 10.
  • livenessProbeUrl: "liveness probe url of nudr-drservice, nudr-notify-service, and ocudr-endpoint". Default value is
  • fqdn: "FQDN of nudr-drservice for NRF to use while sending request. It is carried in registration request to NRF". Default value is ocudr-endpoint.myudr.svc.cluster.local

Table 2-4 Deploying OCUDR in Kubernetes Cluster

Step Description Command
1

To deploy Cloud Native Unified Data Repository in Kubernetes Cluster using the ocudr-custom-values-1.5.0.yaml file. This yaml file is modified by you while referring to the ocudr-custom-values-1.5.0.yaml Parameters table.

helm install <helm chart> [--version <OCUDR version>] --name <release> --namespace <k8s namespace> -f <ocudr-custom-values-1.5.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 OCUDR. 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.5.0 release onwards, all pod names, service name, deployment name are prepended by this release name.
  • <k8s namespace> - is a name of user's choice to identify the kubernetes namespace of the Unified Data Repository. All the Unified Data Repository micro services are deployed in this kubernetes namespace.
  • <ocudr-custom-values-1.5.0.yaml> - is the customized ocudr-custom-values-1.5.0.yaml file. The ocudr-custom-values-1.5.0.yaml file is a part of customer documentation. Users needs to download the file and modify as per the user site.
2 (Optional) Customize the Unified Data Repository by overriding the default values of various configurable parameters. See Customizing Unified Data Repository