[jira] [Commented] (MESOS-809) External control of the ip that Mesos components publish to zookeeper

["Mike Babineau (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MESOS-809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14004099#comment-14004099 ] 

Mike Babineau commented on MESOS-809:
-------------------------------------

Note: this also applies to Schedulers. You can not currently run things like JenkinsScheduler or Marathon from within a container or across network boundaries without jumping through some ugly networking hoops.

> 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.2#6252)