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

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

Hi  David, Thanks for the reply and appologies for the  late reply. Cloudera director ami got corrupted hence i was getting this error. I created a new Cloudera director AMI and now everything works as expected Thanks Anil ... View more

Fixed the issue. I resized the disk space and was able to download and activate the parcel. Thanks for your time and help. ... View more