[
https://issues.apache.org/jira/browse/MESOS-2587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14595313#comment-14595313
]
Tyson Norris commented on MESOS-2587:
-------------------------------------
We see a simliar problem with slaves, where slave MESOS_HOSTNAME is either
reachable by master (using private IP), or else the browser UI works (using
public IP) - but we cannot make both work properly at the same time. Generally
anywhere that HOSTNAME or IP is configurable, this should ideally include a
public and a private value, for networks that expose different values depending
on the actual client.
> libprocess should allow configuration of ip/port separate from the ones it
> binds to
> -----------------------------------------------------------------------------------
>
> Key: MESOS-2587
> URL: https://issues.apache.org/jira/browse/MESOS-2587
> Project: Mesos
> Issue Type: Bug
> Components: libprocess
> Reporter: Cosmin Lehene
>
> Currently libprocess will advertise {{LIBPROCESS_IP}}{{LIBPROCESS_PORT}}, but
> if a framework runs in a container without an an interface that has a
> publicly accessible IP (e.g. a container in bridge mode) it will advertise an
> IP that will not be reachable by master.
> With this, we could advertise the external IP (reachable from master) of the
> bridge from within a container.
> This should allow frameworks running in containers to work in the safer
> bridged mode.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
