[
https://issues.apache.org/jira/browse/MESOS-2902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14626999#comment-14626999
]
Cody Maloney commented on MESOS-2902:
-------------------------------------
One thing as a follow up from the discussion this morning. Generally for
shipping mesos lots of places in DCOS, we're trying to get everything to not
happen on the host we're shipping to. Any code we execute on a host has a high
probability of having some bugs and breaking in a lot of environments. As such,
we bake everything off host, then when it gets to the host itself it's just a
matter of reading static variables whenever possible.
This is effectively pushing possible errors for us from runtime / machine
startup time when we really have a hard time fixing them to configuration setup
time on some remote machine. I can generate a config using some tools. Test it
out locally, and know that the remote machine will behave the same since it
will get the same bit for bit config. If it's some script, I have to predict
what the script will do in the foreign environment (There are very few things
we can rely on existing in the host. Pretty much just bash and curl / wget.
Everything else is additional dependencies we pick up which make it harder to
install DCOS).
> 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)
