[
https://issues.apache.org/jira/browse/MESOS-2587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14543083#comment-14543083
]
Anindya Sinha commented on MESOS-2587:
--------------------------------------
[~clehene] Yes. I think they sound to be the same issues. The basic idea is
that the bind happens on LIBPROCESS_IP and LIBPROCESS_PORT. If these are not
reachable, we need another way for external entities to reach which can be set
based on LIBPROCESS_PUBLIC_IP and LIBPROCESS_PUBLIC_PORT.
> 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)
