09-27-2017 11:09 PM - edited 09-28-2017 02:16 AM
1. I am trying launch a 5 node cluster (aws) using Cloudera Direcotor bootstrap (director ip : say 10.10.10.1). Cloudera director is proxy enabled.
2. I have created a local repository and exposed in some other instance (say http://10.10.10.2/test_repo).
3. I had set NO_PROXY in bash_profile at Cloudera director(10.10.10.1) to access the repository. and I am able to acess it.
cloudera director has a properties file called application.properties in (/etc/cloudera-director-client/)
I have updated the proxy settings in application.properties. but there is no property for NO_PROXY to exclude the IPs.
I have set the repositoryurl property in the config file. while bootstrapping the config file I am getting an error saying service unavailable 503.
Is there anything that i can do to exclude the local repository(10.10.10.2) by setting NO_PROXY in application.properties. Or is ther any other sollution that I can configre?
09-28-2017 10:13 AM
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.