The Cloudera Director Configuration File

The Cloudera Director configuration file is used to launch a cluster through Cloudera Director client with the bootstrap command, or through the Cloudera Director server with the bootstrap-remote command.

For information on the bootstrap and bootstrap-remote commands, see Commands. The configuration file follows the HOCON format. For information on HOCON, see the documentation on GitHub at HOCON (Human-Optimized Config Object Notation).

Location of Sample Configuration Files

Sample configuration files are found either in /usr/lib64/cloudera-director/client or /usr/lib/cloudera-director/client, depending on the operating system you are using. Copy the sample files to your home directory before editing them.

Customizing the Configuration File

Copy the sample files to your home directory before editing them. Rename the cloud_provider.simple.conf or cloud_provider.reference.conf file to your_filename.conf.
  • For simple cluster configuration, use cloud-provider.simple.conf.
  • For advanced cluster configuration, use cloud_provider.reference.conf.
Open your copy of the configuration with a text editor to customize the configuration settings.

The cloud_provider.reference.conf version of the configuration file includes advanced settings that are documented in comments within the file itself. Details on the specific settings in the file are not duplicated in this document.

Valid Role Types for Use in Configuration Files

For a list of valid roles for Cloudera Manager and CDH services that you can use in a Cloudera Director configuration file, see the Cloudera Manager API page on Available Role Types.

Using the API to Import a Configuration File

Beginning with release 2.0 of Cloudera Director, you can import the contents of a configuration file into Cloudera Director with the API using the /api/<api_version>/import endpoint. For example:

In this way, you can POST the contents of a configuration file to Cloudera Director without using the Cloudera Director CLI. The values clusterName, deploymentName, and environmentName are all optional. If they are present, they override the values in the configuration file.