[
https://issues.apache.org/jira/browse/MESOS-2102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14210108#comment-14210108
]
Dominic Hamon commented on MESOS-2102:
--------------------------------------
One thing that's been in the back of my mind, which I think would satisfy this
use case, is to separate the web UI from the master/slave processes. So the
webui would be a standalone process that would have its own flags, endpoint,
etc, and would get the information from the master/slave endpoints.
> Allow configuration of external hostname for web ui
> ---------------------------------------------------
>
> Key: MESOS-2102
> URL: https://issues.apache.org/jira/browse/MESOS-2102
> Project: Mesos
> Issue Type: Improvement
> Components: webui
> Affects Versions: 0.20.1
> Reporter: Lukas Loesche
> Assignee: Joris Van Remoortere
>
> You often have Mesos running in an environment where nodes have internal and
> external IP addresses.
> It would be advantageous for Mesos and Frameworks to do communication using
> the internal IPs while users of the web ui connect to the external IPs.
> At the moment if I set --hostname to the internal hostname that hostname is
> propagated to the web ui and users can't open the slave sandbox. Also the
> redirect to the active master leads to the wrong hostname then.
> If I set --hostname to the external hostname I have to allow Mesos nodes to
> communicate with each other using the public IP.
> The way to work around this at the moment is to configure split DNS or
> /etc/hosts entries.
> It would be nice if I could define something like --webui-hostname or
> --public-hostname so that nodes communicate via the private interfaces.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
