Redpoint Master Data Management (MDM) is a data stewardship system for managing the Golden Record: a single, accurate, and always up-to-date view of your most critical data. The MDM system includes a variety of capabilities for controlling your data,
MDM is packaged and distributed as docker container images that are hosted in the Redpoint Global private repository in Docker Hub.
This documentation will show you how to Install or upgrade MDM in Kubernetes using HELM
- Prerequisites
- System Requirements
- Install Procedure
- Retrieve the MDM URL Endpoints
- Connect MDM to Redpoint Data Management (RPDM)
- Install MDM License
- Get MDM Support
-
MongoDB server sizing
- 4 GB memory for data < 1 million records total:
- 8-16 GB memory for data 1-10 million records total
- SSD disks for best IO perfomance
- Size the MongoDB memory to keep working index set in memory for data > 10 million records total
-
Kubernetes Cluster sizing
- nodepool with 2-3 nodes for high availabilty
- 8 vCPUs and 32 GB memory per node
- 20 GB or more free disk space per node
Before you install MDM, you must:
- Install kubectl. ( https://kubernetes.io/docs/tasks/tools/install-kubectl-linux/ )
- Install HELM. ( https://helm.sh/docs/intro/install/ )
- Have a Kubernetes solution available to use. ( https://kubernetes.io/docs/setup/production-environment/turnkey-solutions/ )
- Have an Ingress Controller solution deployed in your Kubernetes cluster (https://kubernetes.io/docs/concepts/services-networking/ingress-controllers/)
- Have a MongoDB database server available to use for the MDM application Databases. ( https://docs.mongodb.com/v4.4/installation/). This can also be a managed solution like mongo Atlas. (As of this writing, MDM has been tested on MongoDB version 4.4)
- Clone this repository ( git clone https://github.com/RedPointGlobal/rp-mdm.git )
- If you dont have a docker ID, create one at https://hub.docker.com/ and provide Redpoint Support with your account ID so they can grant you permissions to pull the MDM container images
- Have a license key to activate a Trial for Production License. Contact Redpoint support for an activation key
- Clone this repository
git clone https://github.com/RedPointGlobal/rp-mdm.git
- Connect to your Kubernetes Cluster
- Create a namespace for MDM (HELM expects a namespace named redpoint-mdm to exist)
kubectl create namespace redpoint-mdm
- Create the following kubernetes secrets that MDM needs
- mongodb-conn-string : Secret that contains the mongodb connection string
- docker-io : Secret that contains your docker hub credentials
- mdm-tls : Secret that contains your TLS certificate and private key to be used by the Ingress
- Edit the values.yaml file and update the following sections
- ldap : Change the example.com domain to your Active Directory domain
- ingress: Change the host_domain value to the FQDN you want to use for your ingress URLs
- Make sure you are in the repo directory that you cloned in step 1 and then run the following command to insall MDM
helm install redpoint-mdm redpoint-mdm/ --values values.yaml
It may take a few minutes for the all the MDM services to start. Please wait about 10 minutes before testing.
- Execute the command below to get the URL endpoints
kubectl get ingress
- The command returns the following URL endpoints
- rp-mdm-ui.example.com (This is the Web UI endpoint)
- rp-mdm-auth.example.com (This is the authentication server endpoint)
- rp-mdm-core.example.com (This is the core service endpoint )
- To connect MDM to RPDM, you simply install the MDM Tools in RPDM (see MDM and RPDM user guides for more info) and then provide the following
- Authentication Server URL: https://rp-mdm-auth.example.com/mdm
- Core Server URL: https://rp-mdm-core.example.com/mdm
Once you obtain your activation key from Redpoint Support, access the MDM web UI and provide the information below
- Activation Key: Contact Redpoint Global support for an activation key
- License URLs
- For trial/demo: trial-license
- For production: https://qlm1.net/redpointglobal/qlmlicenseserver/qlmservice.asmx
- Public Key: : Same as the activation key
- Product ID: : Prod or Trial depending on your activation key
NOTE: If you get an error applying the license - try again by inputting the same Activation Key for both the Activation Key and Public Key sections
After successful activation, you should see the Welcome page below
Contact [email protected] for any application specific issues you may encounter. Note that Kubernetes specific or other network connectivity errors are out of scope.