ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Greg Hill (JIRA)" <>
Subject [jira] [Commented] (AMBARI-12916) Make API server hostname for views configurable
Date Wed, 09 Mar 2016 14:01:40 GMT


Greg Hill commented on AMBARI-12916:

I don't know about the bootstrapping since we preconfigure our agents with the correct ambari
server hostname, but I did grep the codebase and only the views use the affected codepath,
so the agent bootstrapping must use something else.  The agents in our situation use the local
hostname so agent traffic goes over the private network, btw.  I could see making a separate
config option if you wanted to tell the bootstrapping process which hostname to use for the
agents to talk back to, but that's beyond the scope of this bug, IMO.

> Make API server hostname for views configurable
> -----------------------------------------------
>                 Key: AMBARI-12916
>                 URL:
>             Project: Ambari
>          Issue Type: Improvement
>          Components: ambari-server, ambari-views
>    Affects Versions: 2.1.0
>            Reporter: Greg Hill
>            Assignee: Greg Hill
>            Priority: Minor
>         Attachments: AMBARI-12916.patch
> The views that need to get data from the Ambari API use the system hostname to connect
to the Ambari API.  The problem is that the API could be configured with an SSL cert for a
domain name other than the system hostname, and if you connect to it using the hostname, you
will get SSL validation errors.  Simply adding an optional hostname to the Ambari configs
that will be used here would make it much easier to work in this sort of setup.

This message was sent by Atlassian JIRA

View raw message