Initialize DP Platform

After installing the RPMs and optionally configuring your external database and TLS certificate, you must initialize DataPlane.

1. Navigate to the folder containing the DataPlane configuration script.

   cd /usr/dp/current/core/bin

2. Run system checks needed by DP

   ./dpdeploy.sh system-check

   system-check option allows user to run couple of system checks needed by DPS. When executed, it will check:

   • if the required ports are available
   • if docker client is running and docker daemon is running
   • if SELinux is in permissive mode
   • system firewall settings
   • iptables rules
   • IP Forwarding
3. Initialize the software.
   This loads the Docker images into your local system and prompts for configuration options.

   ./dpdeploy.sh init --all

   You can use disable-system-check flag to skip system checks although it is not a recommended way of installation.

   ./dpdeploy.sh init --all --disable-system-check

4. Create the password for a Super User and a Master Password for the system.
   Ensure that you remember these passwords, as they cannot be retrieved or reset. If you forget the password, contact Hortonworks Support for further assistance.

   Setup the default 'admin' user. This user is for initial setup of DataPlane, including configuration of LDAP and adding additional DPS Admins.
   
   Enter a password for this 'admin' 'user:
   Re-enter password:
   
   Setup a Master password for the DataPlane. The Master password is used to secure the keystore storage for the system.
   Therefore, it is recommended you use a strong password. You will need to provide the Master password for various DataPlane administrative operations.
   
   Important: The Master password cannot be reset easily. Do not forget or misplace.
   
   Enter master password for DataPlane Service (Minimum 6 characters long):
   Reenter password:
   

5. When the initialization process completes, you can check the status of the docker containers using the following command:

   docker ps 

   Sample output:

   IMAGE                                       COMMAND                  CREATED             STATUS              PORTS                                                                      NAMES
   7054de3e2e78        hortonworks/dp-app:1.2.1.0-37               "/bootstrap.sh"          2 minutes ago       Up 2 minutes        0.0.0.0:80->80/tcp, 0.0.0.0:443->443/tcp, 9000/tcp                         dp-app
   c7119441ef77        hortonworks/dp-cluster-service:1.2.1.0-37   "./docker_service_st…"   2 minutes ago       Up 2 minutes        9009-9010/tcp                                                              dp-cluster-service
   7651d09d33d9        hortonworks/dp-db-service:1.2.1.0-37        "./docker_service_st…"   2 minutes ago       Up 2 minutes        9000/tcp                                                                   dp-db-service
   e3bc2ac15dc1        hortonworks/dp-gateway:1.2.1.0-37           "./docker_service_st…"   2 minutes ago       Up 2 minutes        8762/tcp                                                                   dp-gateway
   98bf7858cb13        hortonworks/dp-knox:1.2.1.0-37              "/usr/dp-scripts/kno…"   2 minutes ago       Up 2 minutes        53/udp, 8300-8302/tcp, 8400/tcp, 8301-8302/udp, 8500/tcp                   knox
   05a79ed55f05        consul:1.0.1                                "/bin/sh -c 'mkdir -…"   2 minutes ago       Up 2 minutes        8300-8302/tcp, 8301-8302/udp, 8600/tcp, 8600/udp, 0.0.0.0:8500->8500/tcp   dp-consul-server
   d0cd58aaef00        postgres:9.6.3-alpine                       "docker-entrypoint.s…"   2 minutes ago       Up 2 minutes        5432/tcp                                                                   dp-database     

   Output descriptions:

   Docker Container Name	Description
   dp-app	DP Instance application (UI, web, etc.), accessible from port 443 (port 80 redirects to port 443) by default
   dp-cluster-service	Powers how DP Platform talks to clusters
   dp-db-service	Backend data store API in support of DP Apps
   dp-gateway	Handles routing between DP Platform, DP Apps, Knox, etc.
   knox	Runs a Knox instance that wraps the DataPlane instance. This is the AuthN enforcement point for DataPlane via single sign-on (SSO).
   dp-consul-server	Handles the networking of the containers
   dp-database	The PostgreSQL database instance that the DP instance uses by default. This is not used if you configure DataPlane for an external database.

6. Browse to your DP Instance host and proceed to log in using the Super User admin account.

   	Note
   	If you are using AWS, do not use the public DNS to access DataPlane. Use a public IP address or set up and use a DNS (Route 53) fully qualified domain name (FQDN).

   https://<DP_host_FQDN>

   As part of the installation process, data collection using cookies and other telemetry mechanisms is turned on by default. To disable all data telemetry, see the DataPlane Administration Guide for disabling data telemetry.

   	Note
   	If you get an error message when configuring the platform, destroy the setup by running the ./dpdeploy.sh destroy --all command and restart the initialization process.