mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marco Massenzio (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MESOS-2902) Enable Mesos to use arbitrary script / module to figure out IP, HOSTNAME
Date Wed, 08 Jul 2015 21:32:04 GMT

     [ https://issues.apache.org/jira/browse/MESOS-2902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Marco Massenzio updated MESOS-2902:
-----------------------------------
    Shepherd: Benjamin Hindman

> 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)

Mime
View raw message