ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Luciano Resende (JIRA)" <>
Subject [jira] [Commented] (AMBARI-9100) Reverse-proxy Friendly
Date Fri, 20 Mar 2015 17:04:40 GMT


Luciano Resende commented on AMBARI-9100:

I am interested in working on this issue in the next few weeks, could someone please assign
it to me (I might need to be added to Jira contributor group).

> Reverse-proxy Friendly
> ----------------------
>                 Key: AMBARI-9100
>                 URL:
>             Project: Ambari
>          Issue Type: Improvement
>          Components: ambari-web
>    Affects Versions: 1.7.0
>         Environment: HDP2.2 on Ubuntu 14.04
>            Reporter: Benoit Perroud
>            Priority: Minor
> Ambari is redirecting to native UI (in the quick links for instance) directly to the
hostname:port of that server running the UI. But these UI might not be directly reachable
from where Ambari is accessed -- for instance when Ambari is sitting between a publicly accessible
(internet or corporate LAN) network and a private, Hadoop dedicated network. The same is true
for Nagios and Ganglia services.
> As it is today, it's even hard to do substitution in the reverse proxy to remap the URIs
returned by Ambari to look correct from a user perspective.
> Ambari should be "reverse-proxy friendly", i.e. either it does the proxying itself (for
instance http://ambari:8080/proxy/ganglia proxy to http://internal-ganglia:80/ganglia, http://ambari:8080/proxy/namenode-ui
proxy to http://internal-namenode:50070, etc...), or could let the admin specify a public
URL where she can proxy to the native UIs (using apache httpd mod_proxy or whatever else).

> I found the public_host_name property in the DB, but this seems to be reset by the agent
registration, so it can't be tweaked.

This message was sent by Atlassian JIRA

View raw message