Submitting a Cluster Configuration File
- Through the Cloudera Director server web UI.
- Through the Cloudera Director client, which you can use to send a configuration file that the server uses for cluster deployment. The configuration file provides advanced options not available in the server web UI.
This section describes the second of these ways, using the Cloudera Director client to submit a configuration file. The configuration file will be applied to the cluster and managed by the Cloudera Director server.
When you submit a cluster configuration from a Cloudera Director client to the Cloudera Director server, all communications are transmitted in the clear (including the AWS credentials) unless you use TLS. If the client and server communicate over the Internet, Cloudera recommends that you either use TLS, or use a VPN for security. For information about configuring Cloudera Director to require TLS encryption for access, see TLS for Cloudera Director Itself.
To submit a cluster configuration file to the Cloudera Director server, follow these steps:
- Create a configuration file. See Provisioning a Cluster on AWS.
- Install the latest version of the Cloudera Director client from the Cloudera Director Download Page.
- Enter the following command:
cloudera-director bootstrap-remote myconfig.conf --lp.remote.username=admin --lp.remote.password=admin --lp.remote.hostAndPort=host:portmyconfig.conf is the name of your configuration file, admin is the default value for both the username and password for the Admin account (enter your actual values), host is the hostname or IP address of the instance on which Cloudera Director server is running, and port is the port on which it is listening. The default port for Cloudera Director is 7189.
Both the Cloudera Director client (in the terminal where the bootstrap-remote command was issued) and the Cloudera Director server web UI display the status throughout the deployment process.