[
https://issues.apache.org/jira/browse/MESOS-2902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14619890#comment-14619890
]
Cody Maloney commented on MESOS-2902:
-------------------------------------
Probably we should sync in person tomorrow and summarize on here.
We could potentially say "You have to run a script on every host which sets
LIBPROCESS_IP (Or MESOS_IP which turns into the --ip flag and therefore
LIBPROCESS_IP)". It adds complexity in the form of extra dependencies, and
makes the cluster install + running Mesos not very self-contained.
What I like about having Mesos run a script, is we are able to ship that script
inside the DCOS internal host packaging system to hosts, manage and update it
appropriately inside of DCOS. Anything which doesn't live in there we can't
touch, update, etc. during upgrades.
It's also important to note this affects us both for launching Mesos, as well
as launching DCOS System frameworks (Marathon tries to do the same hostname ->
ip logic inside libprocess and it goes just as badly in a lot of our use cases).
> 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)
