FWIW, I figured this out. It is not configurable, it just looks up the local system hostname. It looks like I can tell the agent to use a custom script to figure out what the agent hostname should be, so I can configure the system with the fqdn as the hostname and inject a script for the agent to get the local hostname and that should hopefully work. I'm going to open a JIRA to suggest that both the agent and server hostnames should be configurable.
Greg From: Greg <greg.h...@rackspace.com<mailto:greg.h...@rackspace.com>> Reply-To: "user@ambari.apache.org<mailto:user@ambari.apache.org>" <user@ambari.apache.org<mailto:user@ambari.apache.org>> Date: Tuesday, August 25, 2015 at 2:30 PM To: "user@ambari.apache.org<mailto:user@ambari.apache.org>" <user@ambari.apache.org<mailto:user@ambari.apache.org>> Subject: COMMERCIAL:Setting the Ambari API hostname in views I'm trying to enable views, but Ambari is automatically configuring them with the local domain hostname that we use for internal cluster traffic, rather than the public fqdn that we use for the Ambari API. Because of this we get an SSL hostname mismatch and the views don't work. I tried setting ambari.server.url to the fqdn, but the view still tries to validate the cert for the local hostname. Is there some way to tell Ambari what hostname to use for all API traffic from the views? Trying to dig through the code to figure out where that value is populated, but no luck so far. Greg
