You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Cosmin Lehene (JIRA)" <ji...@apache.org> on 2015/04/01 23:14:56 UTC
[jira] [Commented] (MESOS-809) External control of the ip that
Mesos components publish to zookeeper
[ https://issues.apache.org/jira/browse/MESOS-809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14391480#comment-14391480 ]
Cosmin Lehene commented on MESOS-809:
-------------------------------------
[~anindya.sinha]
I think that makes sense. I was thinking about a similar approach to enable frameworks to work from Docker containers in bridge mode.
Is your patch available somewhere publicly?
Perhaps we could make a PR. I'd be glad to update, clean and test.
> External control of the ip that Mesos components publish to zookeeper
> ---------------------------------------------------------------------
>
> Key: MESOS-809
> URL: https://issues.apache.org/jira/browse/MESOS-809
> Project: Mesos
> Issue Type: Improvement
> Components: framework, master, slave
> Affects Versions: 0.14.2
> Reporter: Khalid Goudeaux
> Priority: Minor
>
> With tools like Docker making containers more manageable, it's tempting to use containers for all software installation. The CoreOS project is an example of this.
> When an application is run inside a container it sees a different ip/hostname from the host system running the container. That ip is only valid from inside that host, no other machine can see it.
> From inside a container, the Mesos master and slave publish that private ip to zookeeper and as a result they can't find each other if they're on different machines. The --ip option can't help because the public ip isn't available for binding from within a container.
> Essentially, from inside the container, mesos processes don't know the ip they're available at (they may not know the port either).
> It would be nice to bootstrap the processes with the correct ip for them to publish to zookeeper.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)