[
https://issues.apache.org/jira/browse/MESOS-809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anindya Sinha updated MESOS-809:
--------------------------------
Comment: was deleted
(was: Mesos master/slave (libprocess) binds to ip:port indicated via
environment vars LIBPROCESS_IP and LIBPROCESS_PORT (or via the --ip, --port in
command line args). If they are private IPs, then this node is not reachable
from outside such as schedulers so we need a publically accessible IP:Port such
that the master/slave is reachable from another node.
In this case, the publically accessible IP:Port should be specified via the
environment variables LIBPROCESS_ADVERTISE_IP and LIBPROCESS_ADVERTISE_PORT (or
on the master can be specified via the command line args --advertise_ip,
--advertise_port). Note that MESOS-3809 shall add these command line args to
mesos slave as well.... till then, you can use the environment vars.
Hope this helps.
)
> 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
> Assignee: Anindya Sinha
> Priority: Minor
> Fix For: 0.24.0
>
>
> 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)
