Sankaranarayanan,   Cloudera Director does not support proxy exclusions.    This like likey most easily configured on your proxy server. The proxy server should have a configuration to not proxy local addresses.   David ... View more

ebeb,   Cloudera Director is designed for provisioning cloud clusters and cannot create a mixed cloud/on-premise cluster.   My initial thoughts on a mixed cluster is that network latency between the cloud nodes and on-premise nodes would lead to poor performance. You may be better served by creating two separate clusters and using some other mechanism for sharing data. For example, you can export/import data to S3.     ... View more

Director uses the IP address and hostnames reported back by the cloud provider (e.g., AWS) to connect to the instance. If Director is inside the same VPC as the instance, this will be the internal IP address or private hostname. If Director is outside the VPC, then this will be the public IP or public hostname.   Since these values come from the cloud provider, it is best for them to be set as you like when the instance is allocated. Some possible suggestions for doing so are to use a custom DNS server or to bake some hostname assignment logic into your AMI.     ... View more

David,   The "bootstrap" and "bootstrap-remote" commands are completely different. The "bootstrap" command will create a deployment and cluster without a Director server, storing the models in a local database file. There is no way to re-use these models across multiple "bootstrap" commands. "bootstrap-remote" submits the deployment and cluster to a Director server and the models will be stored in the Director server database.   See Cloudera Director Interfaces for more information about the distinction between the CLI and the Stand-alone Client.   You can modify your workflow in the following manner:   Please use the bootstrap-remote command in your step 1.   In step 2, you can terminate the cluster in the Director UI. This will leave CM running.   The existing CM will be re-used if you re-run bootstrap-remote with the same conf file or a different conf file that specifies the same "environmentName" and "deploymentName".     ... View more

WZ,   Service names must be globally unique in Cloudera Manager. Director appends random characters to ensure that this uniqueness when creating services in case there are multiple clusters created under the same Cloudera Manager. There is no way to turn off this randomization in Director at the moment and there is no way to rename a service in Cloudera Manager (you can rename the display name only).   Since Director supports only a single instance of each service type, you can retrieve the list of services from Cloudera Manager and create a mapping from service type to service name for your cluster.   In bash, you can use jq to process the service list to retrieve the service names. $ curl -u cmusername:cmpassword http://<cmhost>:7180/api/v15/clusters/<clustername>/services | jq -r '.items[] | "export \(.type)=\(.name)"' > export_service_names.sh $ cat export_service_names.sh export ZOOKEEPER=CD-ZOOKEEPER-asdna2f you can then script against well known servicename variables by sourcing this export_service_names.sh script.   You can similarly retrieve the service names using the java client or python client.     ... View more