Install Mesos (http://mesos.apache.org/) and configure mesos master and slave. This cookbook also supports installation by both bulding from source and with Mesosphere package. You can switch installation type using the node[:mesos][:type] attribute (source or mesosphere).

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

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

You have to specify intallation type (source or mesosphere) by setting node[:mesos][:type] variable.

Currently this cookbook defaults to build mesos from source, i.e. node[:mesos][:type] is set to source.

Install mesos using build_from_source recipe or mesosphere recipe, depending on what the node[:mesos][:type] attribute is set to (source or mesosphere).

Install mesos (download zip from github, configure, make, make install).

Install mesos using Mesosphere's mesos package. You can also install zookeeper package by node[:mesos][:mesosphere][:with_zookeeper] if required because Mesosphere's mesos package doesn't include zookeeper. You can also specify mesosphere package's build version (see below for details).

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

• node[:mesos][:prefix]/var/mesos/deploy/masters
• node[:mesos][:prefix]/var/mesos/deploy/slaves
• node[:mesos][:prefix]/var/mesos/deploy/mesos-deploy-env.sh
• node[:mesos][:prefix]/var/mesos/deploy/mesos-master-env.sh

If you choose mesosphere as node[:mesos][:type], the node[:mesos][:prefix] attribute will be overridden to /usr/local, which is because the package from Mesosphere installs mesos into that directory.

Furthermore, this recipe will also configure upstart configuration files.

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

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

If you have a configuration as shown below:

node[: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 here for available options or the output of mesos-master --help.

Configure slave configuration files, and start mesos-slave.

• node[:mesos][:prefix]/var/mesos/deploy/mesos-slave-env.sh

If you choose mesosphere as node[:mesos][:type], the node[:mesos][:prefix] attribute will be overridden to /usr/local, which is because the package from Mesosphere installs mesos into that directory by default.

Furthermore, this recipe also configures upstart configuration files.

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

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

node[: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 here for available options or the output of mesos-slave --help.

Install mesos-docker executor. Currently only Mesos 0.14.0 is supported.

NOTE: This cookbook DOES NOT install docker automatically. So, you need to install docker manually. See ./example/mesosphere/Vagrantfile

Please see below:

• everpeace/vagrant-mesos
• ./example/source
• ./example/mesosphere

There are a couple of test suites

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

in place, which tests both source and mesosphere installations (as well as master and slave recipes).

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

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.