[
https://issues.apache.org/jira/browse/MESOS-809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13849710#comment-13849710
]
Maciej Pasternacki commented on MESOS-809:
------------------------------------------
To continue - it may be not clear from what I wrote, what would I consider to
be a 100% solution (and I don't have a clear image of how would it look
either). A perfect solution would be one where I can easily put in front of
Mesos master or a cluster of these: NAT, a proxy (possibly implementing access
control and/or encryption), a load balancer, or any Rube Goldberg combination
of the above (like I can just now in case of most HTTP based services). The
same would be possible for slaves; in particular, I'd be able to set up an
authenticated front for Mesos web UI that I could access from the world, and
which wouldn't require me to leave my slaves' port 5051 wide open.
> 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.1.4#6159)
