It looks as though you're specifying the incorrect credentials for the instance that you're using. Often the intended initial username can differ with the AMI, e.g. many CentOS images use "centos" as the username, RHEL often use "ec2-user", etc. Are you using EC2 for this deployment? If so, what AMI are you using and on what region? ... View more

Funny enough, I actually just ran into this myself. You should be able to do this by setting this hue_service_safety_valve service level config for Hue. If you're using a config file: cluster { .... configs { .... HUE: { hue_service_safety_valve: """ [desktop] allowed_hosts=* """ } } .... } Note that I haven't totally tested this myself yet, but I'll actually go ahead and do this right after this reply and confirm. ... View more

It's good to hear that you're looking into this. I don't think we have a lot of API users at the moment, so your feedback will be very useful to us. So you'll really need PUT for the cluster template in order to make an update rather than the cluster object. The cluster object is a bit more ephemeral in nature and reflects the current active state of the cluster. Are you using one of the SDKs (https://github.com/cloudera/director-sdk, only available in Java/Python)? It sounds like you're doing something a little more manual, but I'd encourage you to use those if possible. Otherwise, the API console is probably your best bet for documentation at the moment. Assuming Director is running on your local machine, you'd navigate to: http://localhost:7189/api-console Let me know if that points you in the right direction. ... View more

There is, actually! In the cloudera-manager section, you can set javaInstallationStrategy to NONE:   ... cloudera-manager { javaInstallationStrategy: NONE ... } Keep in mind that you'll need to install Java yourself, either by including it with your AMI of choice or using a bootstrap script. If you use a bootstrap script, you may be interested in this instance bootstrap script sample, which will install Java 8 on your Cloudera Manager/cluster. ... View more

Give that Cloudera Manager was provisioned using Director, I don't think we want to go down the route of supplying a CM URL.   What @jadair was saying is that instead of   deploymentName: My_Test" Deployment" environmentName: myCM" Environment" try: deploymentName: "My_Test Deployment" environmentName: "myCM Environment" Also, the question about verifying the names of the deployment/environment are still relevant here. The name of the deployment and environment aren't necessarily suffixed with Deployment and Environment -- they can be named arbitrarily. By default, however, the Director client suffixes deployment and environment names with those strings.   Finally, you may have to specify an image for this CM, even though it won't get used. This is due to a limitation on how we do our validation. For example: deploymentName: "My_Test Deployment" environmentName: "myCM Environment" ... instances { cm-image { type: m3.xlarge image: ami-6283a827 } } .... cloudera-manager { instance: ${instances.cm-image} { tags { application: "Cloudera Manager 5" } } .... username: "my_username" password: "my_password" } Let me know if any of this helps. ... View more