You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Bjoern Metzdorf (JIRA)" <ji...@apache.org> on 2015/05/12 19:33:01 UTC
[jira] [Commented] (MESOS-2587) libprocess should allow
configuration of ip/port separate from the ones it binds to
[ https://issues.apache.org/jira/browse/MESOS-2587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14540296#comment-14540296 ]
Bjoern Metzdorf commented on MESOS-2587:
----------------------------------------
Hey guys, any chance that this gets merged soon? It's really useful!
> 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)