Prior to starting the DPS Installation, you must download the DPS repository tarballs (i.e. the “product binaries”) from the Hortonworks Customer Portal following the instructions provided as part of the subscription fulfillment process. DPS Platform and the DPS Apps (and related Agents) are provided as RPMs in tarball repositories.
Your system must be configured for both forward and reverse DNS.
Every host name used with DPS must be resolvable by DNS or configured in the /etc/hosts file on the DPS container, so that host names can be resolved between all cluster nodes. Using a DNS server is the recommended method, but if the instances are added to /etc/hosts, you must explicitly register the cluster host names within the DPS Docker containers. It is not sufficient to have the host names included in the /etc/hosts file on the DPS Platform host. See the DPS Platform Administration guide for instructions.
If you are using AWS, do not use the public DNS to access DPS. Use a public IP address or set up and use a DNS (Route 53) fully qualified domain name (FQDN).
The DP Host requires the following ports to be available on the host:
|80, 443||The DP Instance Web UI. Port 80 is redirected to port 443 for SSL. Refer to Configuring DPS Platform to configure your own certificate.|
|8500||Used by Consul which handles the Docker container networking.|
You must disable SELinux enforcement of permissions before installing the DPS service, due to an issue with SELinux and Docker.
If you do not disable SELinux, then DPS will not install and run properly, and you will have to destroy and reinstall the containers.
setenforce 0 #A zero, not a letter sed -i 's/^SELINUX=.*/SELINUX=disabled/g' /etc/sysconfig/selinux
The second command prevents SELinux from being automatically re-enabled after a reboot.
Docker containers are used to install each DPS service. You must install either Docker Enterprise Edition (EE) or Community Edition (CE). You might be required to reboot your system after installing Docker.
For general information about installing Docker, see Install Docker.
You need access to an enterprise LDAP setup when configuring DPS. Refer to Enterprise LDAP requirements for more information on the LDAP settings and options.
By default, DPS Platform includes an embedded PostgreSQL instance for testing and evaluation purposes only. You should configure your DP instance to use an external PostgreSQL instance. We strongly recommend configuring DPS Platform with an existing external database when running in production, and not use the embedded PostgreSQL. Refer to Configuring DPS Platform for more information.