Forge Home


Module that manages the Marathon framework for Mesos


1,209,489 latest version

5.0 quality score

Version information

  • 0.4.2 (latest)
  • 0.4.1
  • 0.4.0
  • 0.3.0
  • 0.2.0
  • 0.1.1
released Mar 18th 2016
This version is compatible with:
  • Puppet Enterprise 2021.4.x, 2021.3.x, 2021.2.x, 2021.1.x, 2021.0.x, 2019.8.x, 2019.7.x, 2019.5.x, 2019.4.x, 2019.3.x, 2019.2.x, 2019.1.x, 2019.0.x, 2018.1.x, 2017.3.x, 2017.2.x, 2017.1.x, 2016.5.x, 2016.4.x
  • Puppet >=3.4.0
  • , ,

Start using this module

  • r10k or Code Manager
  • Bolt
  • Manual installation
  • Direct download

Add this module to your Puppetfile:

mod 'praekeltfoundation-marathon', '0.4.2'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add praekeltfoundation-marathon
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install praekeltfoundation-marathon --version 0.4.2

Direct download is not typically how you would use a Puppet module to manage your infrastructure, but you may want to download the module in order to inspect the code.



praekeltfoundation/marathon — version 0.4.2 Mar 18th 2016


Forge Build Status

A Puppet module for configuring Marathon

This module was designed for Marathon version 0.13.0+. Older versions should still work but may require some extra configuration.

This module has been tested on:

  • Ubuntu 14.04 running Puppet 3.4 and 3.8
  • RHEL 7 running Puppet 3.7

Again, this should work on other setups but we make no promises.

Getting started

The module should be immediately familiar to anybody who has used the deric/mesos module.

class { 'marathon':
  zookeeper   => 'zk://',
  master      => 'zk://',
  options     => {
    hostname         => $::hostname,
    event_subscriber => 'http_callback',

For information about all the available parameters see the documentation for the class.

Marathon + Mesos

This module reuses large parts of the deric/mesos module and as such that module is a dependency. That module is also our recommended way to manage Mesos with Puppet.

NOTE: There is a conflict when installing both Mesos and Marathon using these modules as both packages are generally installed from the same repository. To work around these conflicts, it is possible to disable the management of the repo by the Marathon module.

For example:

class { 'mesos':
  repo   => 'mesosphere',
  master => $mesos_zk

class { 'marathon':
  repo_manage => false,
  zookeeper   => $marathon_zk,
  master      => $mesos_zk,

Class['mesos::repo'] -> Package['marathon']

Two things to note:

  1. The repo_manage => false line ensures that the Marathon module doesn't try to configure a repo that conflicts with the Mesos one.
  2. We must specify the repo dependency for the Marathon package as there is no way for the Marathon module to know this dependency if it is not managing the repo itself.

Marathon logging

Like any good Java program (technically, Scala), Marathon uses loggers that are configured using a file specified in the JVM's classpath at runtime. This module takes care of configuring this logging for certain versions of Marathon.

To disable the configuration of logging (enabled by default), pass manage_logger => false. Even with management of loggers enabled Marathon will still output to syslog (although this depends on exactly how Marathon is launched).

NOTE: At this time, the logging configuration only works for versions 0.13.0+ of Marathon. Marathon recently switched from log4j to slf4j + logback. This module only includes a configuration file template for logback.