Chapter 8. Reference
Installation Configuration Properties
During installation, you can access the DPS
/usr/dp/current/core/bin/config.env.sh file to modify
configuration properties.
The following list describes the installation configuration properties that you can set.
| Configuration Item | Description | Default Value |
|---|---|---|
USE_EXT_DB | Set to yes for pointing to an external Postgres
instance, no otherwise | no |
DATABASE_URI | If USE_EXT_DB is yes, this must point to
the external Database URI | |
DATABASE_USER | If USE_EXT_DB is yes, this must point to
the DataPlane Admin user name of the external Database URI | |
DATABASE_PASS | If USE_EXT_DB is yes, this must point to
the DataPlane Admin password of the external Database URI | |
SEPARATE_KNOX_CONFIG | Set to true if a separate Knox instance is setup on HDP
clusters for handling DPS traffic, false otherwise | false |
KNOX_CONFIG_USING_CREDS | If SEPARATE_KNOX_CONFIG is true, when a
cluster is registered, we must provide additional information to
discover it. This is either using Ambari credentials or explicitly
specifying the URL. Set to true if you want to use Ambari
credentials, false for URL | true |
CONSUL_HOST | Set to the IP address of the host where DPS containers are launched | |
USE_TEST_LDAP | Specifies whether to use an external LDAP instance or connect to a test LDAP instance that comes with the DataPlane Knox container | |
USE_TLS | Set to true to enable TLS / HTTPS (SSL) | |
USE_PROVIDED_CERTIFICATES | Set to yes if you have public-private key-pair already
generated/issued. Setting to no automatically generates a
key-pair for you. | |
PUBLIC_KEY_L | If USE_PROVIDED_CERTIFICATES is yes, this
must point to the absolute path of public key file | |
PRIVATE_KEY_L | If USE_PROVIDED_CERTIFICATES is yes, this
must point to the absolute path of encrypted private key file |
dpdeploy.sh Script Command Reference
You use the script dpdeploy.sh to deploy and configure DPS Platform during installation.
To use the tool, change to the directory to
/usr/dp/<version>/core/bin and execute as
./dpdeploy.sh <command>
The following table shows the actions that are supported by the script.
| Command | Options | Default Value |
|---|---|---|
| init | [ --all ] | Initialize and start all containers for the first time |
| migrate | Reset database to its pristine state and run schema migrations on it | |
| utils add-host | <ip> <host> | Append a single entry to /etc/hosts file of the
container interacting with HDP clusters |
| utils update-user | [ ambari / atlas / ranger ] | Update user credentials for services that DataPlane will use to connect to clusters |
| utils reload-apps | Restart all containers other than database, Consul and Knox | |
| start | [ --all ] | Start all containers (existing data is retained) |
| stop | [ --all ] | Stop all containers (existing data is retained) |
| ps | List the status of associated docker containers | |
| logs | <container_name> | Logs of supplied container id or name |
| destroy | [ --all ] | Kill all containers and remove them. Needs to start from init again. Deletes all data in the container |
| load | Load all images from ../lib directory into docker
daemon | |
| upgrade | --from <old_setup_directory> | Upgrade existing dp-core to current version |
| version | Print the version of DPS |