[
https://issues.apache.org/jira/browse/MESOS-2902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14619403#comment-14619403
]
Marco Massenzio commented on MESOS-2902:
----------------------------------------
While adding a flag {{ -- ip-detection}} is largely trivial, I think making it
a "required" one would be pretty hard, as it would break countless current
deployments.
As far as having "users see what Mesos is doing" I guess we can add more
logging (assuming it's not already there) and then it's up to the log
aggregation facility (or lack thereof) to wean out meaning from those.
The flag would have a {{native}} default value which would be essentially the
current mechanism - if different, it would execute the given script and then
expect a single string output that would be interpreted as the hostname
(stripped of all leading and trailing spaces).
In other words, the same as running {{/usr/bin/hostname}}.
> 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
> 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)
