ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Levas (JIRA)" <>
Subject [jira] [Commented] (AMBARI-12916) Make API server hostname for views configurable
Date Tue, 08 Mar 2016 20:04:40 GMT


Robert Levas commented on AMBARI-12916:


I now have a better understanding of your issue and the need for your change.  You are correct
in that the name of the variable ({{masterHostname}}) is confusing.

One thing that is still unclear to me is why this change is only relevant for Views.  Doesn't
SSL certificate verification come into play for Ambari agents as well? Shouldn't they use
the a specific hostname when communicating with the Ambari server? If so, we need to make
sure that when Ambari is bootstrapping the agents, it properly configures them with the _correct_
Ambari sever hostname. 

> 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