[
https://issues.apache.org/jira/browse/MESOS-2902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14627033#comment-14627033
]
Vinod Kone commented on MESOS-2902:
-----------------------------------
I'm curious how you do configuration management in DCOS. Do you have one type
of package (rpm, deb etc) that gets shipped which has configuration baked into
the package? I'm assuming no, because each deployment would need some bits of
configuration that are unique (master/zk url, resources etc)? Also, have you
considered running the ip detection script as a post-install hook of your
package installer?
I'm asking because as others have mentioned, adding a one-off thing for a
specific flag is hacky and we would like to really avoid it if we can. While
the effort to maintain such a work around might seem trivial now, when more
people do more one-offs like this the codebase becomes really unmaintenable
down the line.
> 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)
