[
https://issues.apache.org/jira/browse/MESOS-2902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14641048#comment-14641048
]
Benjamin Hindman commented on MESOS-2902:
-----------------------------------------
We've added --ip_discovery_command to _only the master_ in the following commit
(we still need to add it to the slave). I'm going to put this back into 'In
Progress' while we fix this up for the slave too.
commit 37f8545acb3159020c79306cab899e357fcf73a7
Author: Marco Massenzio <ma...@mesosphere.io>
Date: Fri Jul 24 12:33:21 2015 -0700
Enabling IP Discovery command.
JIRA: MESOS-2902
It is sometimes useful to enable an external script to configure the
IP address the Mesos Master will bind to on the server, where it's not
desirable to set the --ip flag and/or a "wrapper" script is not a
viable option.
This patch adds an --ip_discovery_command to point to a local script
that will emit as its only output the IP address that the Master will
bind to: only spaces and newlines are allowed; further, as we cannot
use the `libprocess` sub-processing facilities, we cannot timeout
the script, should this block for long times (or even forever).
This will conflict with the --ip flag, so if both set, we will fail
with an appropriate error message.
Review: https://reviews.apache.org/r/36425
> Enable Mesos to use arbitrary script / module to figure out IP, HOSTNAME
> ------------------------------------------------------------------------
>
> Key: MESOS-2902
> URL: https://issues.apache.org/jira/browse/MESOS-2902
> Project: Mesos
> Issue Type: Improvement
> Components: master, modules, slave
> Reporter: Cody Maloney
> Assignee: Marco Massenzio
> Priority: Critical
> Labels: mesosphere
>
> Currently Mesos tries to guess the IP, HOSTNAME by doing a reverse DNS
> lookup. This doesn't work on a lot of clouds as we want things like public
> IPs (which aren't the default DNS), there aren't FQDN names (Azure), or the
> correct way to figure it out is to call some cloud-specific endpoint.
> If Mesos / Libprocess could load a mesos-module (Or run a script) which is
> provided per-cloud, we can figure out perfectly the IP / Hostname for the
> given environment. It also means we can ship one identical set of files to
> all hosts in a given provider which doesn't happen to have the DNS scheme +
> hostnames that libprocess/Mesos expects. Currently we have to generate
> host-specific config files which Mesos uses to guess.
> The host-specific files break / fall apart if machines change IP / hostname
> without being reinstalled.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
