Adoptable Cookbooks List

Looking for a cookbook to adopt? You can now see a list of cookbooks available for adoption!
List of Adoptable Cookbooks

Supermarket Belongs to the Community

Supermarket belongs to the community. While Chef has the responsibility to keep it running and be stewards of its functionality, what it does and how it works is driven by the community. The chef/supermarket repository will continue to be where development of the Supermarket application takes place. Come be part of shaping the direction of Supermarket by opening issues and pull requests or by joining us on the Chef Mailing List.

Select Badges

Select Supported Platforms


et_mesos (13) Versions 5.0.1

Installs/Configures mesos

cookbook 'et_mesos', '= 5.0.1'
cookbook 'et_mesos', '= 5.0.1', :supermarket
knife supermarket install et_mesos
knife supermarket download et_mesos
Quality 100%

Mesos Cookbook Build Status

Install Mesos ( and configure mesos master and slave. This cookbook installs Mesos using Mesosphere packages.

All credit to @everpeace for the basis for this cookbook, everpeace/cookbook-mesos.


Currently only supports ubuntu and centos. But centos support is experimental.

If you would use cgroups isolator or docker containerizer, Ubuntu 14.04 is highly recommended. Note that docker containerizer is only supported by Mesos 0.20.0+.



Install Java and Mesos, with platform-dependent switches in place.


Install Mesos using Mesosphere's mesos package. You can also install zookeeper package by node['et_mesos']['package']['with_zookeeper'] if required because Mesosphere's Mesos package doesn't necessarily include ZooKeeper.

For a production use case, however, instead of setting that attribute to true, one should use the zookeeper cookbook to provision a well-configured ZooKeeper instance or cluster of instances. There is a caveat to this: the mesos package on Ubuntu installs the zookeeper package, so co-locating Mesos and ZooKeeper using that cookbook is tricky, at best. A separate ZK cluster is encouraged.


Configure master and cluster deployment configuration files, and start mesos-master.

  • node['et_mesos']['deploy_dir']/masters
  • node['et_mesos']['deploy_dir']/slaves
  • node['et_mesos']['deploy_dir']/
  • node['et_mesos']['deploy_dir']/

Furthermore, this recipe will also configure upstart configuration files.

  • /etc/mesos/zk
  • /etc/defaults/mesos
  • /etc/defaults/mesos-master

How to configure mesos-master

You can configure mesos-master command line options using the node['et_mesos']['master'] attribute.

If you have a configuration as shown below:

node['et_mesos']['master'] = {
  port:    "5050",
  log_dir: "/var/log/mesos",
  zk:      "zk://localhost:2181/mesos",
  cluster: "MyCluster",
  quorum:  "1"

Then mesos-master will be invoked with command line options like this:

mesos-master --zk=zk://localhost:2181/mesos --port=5050 --log_dir=/var/log/mesos --cluster=MyCluster

See the latest Mesos config docs for available options or the output of mesos-master --help.


Configure slave configuration files, and start mesos-slave.

  • node['et_mesos']['deploy_dir']/

Furthermore, this recipe also configures upstart configuration files.

  • /etc/mesos/zk
  • /etc/defaults/mesos
  • /etc/defaults/mesos-slave

How to configure mesos-slave

You can configure mesos-slave command line options by node['et_mesos']['slave'] hash. If you have a configuration as shown below:

node['et_mesos']['slave'] = {
  master:         'zk://localhost:2181/mesos',
  log_dir:        '/var/log/mesos',
  containerizers: 'docker,mesos',
  isolation:      'cgroups/cpu,cgroups/mem',
  work_dir:       '/var/run/work'

Then mesos-slave will be invoked with command line options like this:

mesos-slave --master=zk://localhost:2181/mesos --log_dir=/var/log/mesos --containerizers=docker,mesos --isolation=cgroups/cpu,cgroups/mem --work_dir=/var/run/work

See the latest Mesos config docs for available options or the output of mesos-slave --help.


Wrap this cookbook and include_recipe 'et_mesos::master' or include_recipe 'et_mesos::slave', depending on what part of the cluster you need to provision.

The recommendation would be to have two wrapper cookbooks, one for the master(s), and another for your slave(s).


<table> <tr> <th>Key</th> <th>Type</th> <th>Description</th> <th>Default</th> </tr> <tr> <td><tt>['et_mesos']['version']</tt></td> <td>String</td> <td>Version(branch or tag name at <a href=""></a>).</td> <td><tt>0.22.1</tt></td> </tr> <tr> <td><tt>['et_mesos']['package']['with_zookeeper']</tt></td> <td>String</td> <td>Flag for installing zookeeper package</tt>.</td> <td><tt>false</tt></td> </tr> <tr> <td><tt>['et_mesos']['ssh_opt']</tt></td> <td>String</td> <td>ssh options to be used in <tt>mesos-[start|stop]-cluster</tt></td> <td><tt>-o StrictHostKeyChecking=no <br> -o ConnectTimeout=2</tt></td> </tr> <tr> <td><tt>['et_mesos']['deploy_with_sudo']</tt></td> <td>String</td> <td>Flag whether sudo will be used in <tt>mesos-[start|stop]-cluster</tt></td> <td><tt>1</tt></td> </tr> <tr> <td><tt>['et_mesos']['cluster_name']</tt></td> <td>String</td> <td>[OBSOLETE] Human readable name for the cluster, displayed at webui. </td> <td><tt>MyCluster</tt></td> </tr> <tr> <td><tt>['et_mesos']['master_ips']</tt></td> <td>Array of String</td> <td>IP list of masters used in <tt>mesos-[start|stop]-cluster</tt></td> <td>[ ]</td> </tr> <tr> <td><tt>['et_mesos']['slave_ips']</tt></td> <td>Array of String</td> <td>IP list of slaves used in <tt>mesos-[start|stop]-cluster</tt></td> <td>[ ]</td> </tr> <tr> <td><tt>['et_mesos']['master']['zk']</tt></td> <td>String</td> <td>[REQUIRED(0.19.1+)] ZooKeeper URL (used for leader election amongst masters). May be one of:<br> zk://host1:port1,host2:port2,…path<br> zk://username:password@host1:port1,host2:port2,…/path<br> file://path/to/file (where file contains one of the above)</td> <td></td> </tr> <tr> <td><tt>['et_mesos']['master']['work_dir']</tt></td> <td>String</td> <td>[REQUIRED(0.19.1+)] Where to store the persistent information stored in the Registry.</td> <td><tt>/tmp/mesos</tt></td> </tr> <tr> <td><tt>['et_mesos']['master']['quorum']</tt></td> <td>String</td> <td>[REQUIRED(0.19.1+)] The size of the quorum of replicas when using “replicated_log” based registry. It is imperative to set this value to be a majority of masters, i.e., quorum > (number of masters) / 2.</td> <td></td> </tr> <tr> <td><tt>['et_mesos']['master']['option_name']</tt></td> <td>String</td> <td>You can set arbitrary command line option for <tt>mesos-master</tt>, replace option_name with the key for the option to set. See the <a href="">latest Mesos config docs</a> for available options, or the output of mesos-master --help.</td> <td></td> </tr> <tr> <td><tt>['et_mesos']['slave']['master']</tt></td> <td>String</td> <td>[REQUIRED] mesos master url.This should be a zk:// style address.</td> <td></td> </tr> <tr> <td><tt>['et_mesos']['slave']['option_name']</tt></td> <td>String</td> <td>Like <tt>['et_mesos']['master']['option_name']</tt> above, arbitrary options may be specified as a key for a slave by replacing option_name with your option’s key.</td> <td></td> </tr> </table>


There are a couple of test suites in place:

  • chefspec for unit tests.
  • test-kitchen with serverspec for integration tests (using kitchen-ec2).


  1. Fork the repository on Github
  2. Create a named feature branch (like add_component_x)
  3. Write you change
  4. Write tests for your change (if applicable)
  5. Run the tests, ensuring they all pass
  6. Submit a Pull Request using Github


MIT License. see [LICENSE.txt](LICENSE.txt)

(Please note that before 2015-02-06-18:00 PST, this project is opened under Apache License, Version 2.0. See also in old version)

Foodcritic Metric

5.0.1 passed this metric