[
https://issues.apache.org/jira/browse/MESOS-2902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14619848#comment-14619848
]
Marco Massenzio commented on MESOS-2902:
----------------------------------------
well, I'm now genuinely confused: given that
{quote}
I could make a new mesos-init-fetch-ip script which I run instead of mesos, and
that script then execs mesos. This confuses init system tracking of processes
somewhat, and obfuscates what the underlying commands being run are.
{quote}
what's wrong with:
{code}
./bin/mesos-master.sh --ip=`mesos-init-fetch-ip`
--hostname='mesos-init-fetch-hostname` --zk=zk://...
{code}
I thought you were objecting to the master trying to guess its hostname by
either using {{os::hostname()}} and/or using DNS on its {{/etc/hostname}} to
discover its own IP.
Alternatively, you can use a startup script to set {{LIBPROCESS_IP}} and be
done with it (sure, typos and other snafu's are always possible, but, hey,
that's what integration tests are for).
> 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)
