[
https://issues.apache.org/jira/browse/MESOS-2102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16583101#comment-16583101
]
Benjamin Mahler commented on MESOS-2102:
----------------------------------------
[~Kjelle] since this ticket was filed, we've centralized all the master and
agent routing into single functions. You can see how DC/OS adapts the mesos ui
to work with it here:
https://github.com/dcos/dcos/blob/4961d8182917d102284f7a0ccc29e4c422913565/packages/mesos/extra/patches/0003-Mesos-UI-updated-the-URL-generation-to-make-it-work-.patch
Users can customize these to their own needs, but ideally they can do this
without having to patch the code. If you have any thoughts here they would be
appreciated.
> 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
> Priority: Major
> Labels: mesosphere
>
> 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
(v7.6.3#76005)
