[
https://issues.apache.org/jira/browse/MESOS-2587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14540353#comment-14540353
]
Cosmin Lehene commented on MESOS-2587:
--------------------------------------
[~nnielsen] - I created this after a discussion on IRC which got me to
MESOS-809. It seems [~anindya.sinha] may have a patch for this as well based on
comments in the other thread, but that didn't get any updates after the last
comment...
If there's no patch, depending on the effort required to get this into
libprocess (I thought it should be relatively easy, but I'm not familiar with
the codebase so input from someone more knowledgeable would be appreciated) vs
the progress with the new HTTP API which may solve this indirectly we can
discuss it.
> 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
> Fix For: 0.23.0
>
>
> 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)
