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

["Maciej Pasternacki (JIRA)" <ji...@apache.org>]

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

Maciej Pasternacki commented on MESOS-809:
------------------------------------------

The good enough 80% solution would be just to support --public_ip and --public_port options. This would make it possible to use a single Mesos cluster across EC2 regions, or behind NAT. With Docker scenario, host starting the container knows the public IP and can force the public port, and pass these as environment variables to the container.

An extra benefit (with a bit of performance penalty, though) would be to allow to announce a DNS name rather than IP. This is important in split horizon DNS environments such as EC2: EC2 instance's public hostname resolves to local IP from within the same data center, and to its public world-routable IP from the outside. This may affect cost, as it's likely that bandwidth on world-routable public IP counts as external traffic even if it comes from within the same region.

> 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)