[MESOS-2902] Enable Mesos to use arbitrary script / module to figure out IP, HOSTNAME

• Type: Improvement
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Fix Version/s: 0.24.0
• Component/s: agent, master, modules
• Labels: mesosphere
• Target Version/s: 0.24.0
• Sprint: Mesosphere Sprint 15
• Story Points: 5
• Assignee: Marco Massenzio
• Reporter: Cody Maloney
• Shepherd: Benjamin Hindman
• Created: 19/Jun/15 21:36
• Updated: 29/Apr/19 09:26
• Resolved: 26/Nov/18 12:54

Description

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.

Issue Links

• is related to: MESOS-3366 Allow resources/attributes discovery