Application cookbook for installing the Apache Mesos cluster manager. Mesos provides efficient resource isolation and sharing across distributed applications, or frameworks. This cookbook installs Mesos via packages provided by Mesosphere.
- Chef >= 12.14.60
Tested on
- Ubuntu 16.04
- Ubuntu 15.10
- Ubuntu 14.04
- Ubuntu 12.04
- Debian 8.6 (with Java 7)
- CentOS 7.2
- CentOS 6.8
This cookbook is tested against the following Apache Mesos versions:
- 1.1.0
- 1.0.1
- 1.0.0
We intend to support at most the three latest versions of Apache Mesos.
In order to keep the README managable and in sync with the attributes, this cookbook documents attributes inline. The usage instructions and default values for attributes can be found in the individual attribute files.
This cookbook introduces a few points of validation to prevent passing Mesos
invalid configuration options. The ruby block
mesos-slave-configuration-validation and
mesos-master-configuration-validation extract a hash of all valid Mesos
configuration options from the --help output of the master and slave binary
and check it against the provided attributes. This cookbook will fail to
converge if you try to use an invalid configuration option as a command line
flag attribute under ['mesos']['master']['flags']
or ['mesos']['slave']['flags'] hashes.
The valid list of Mesos options may be found at: https://github.com/apache/mesos/blob/master/docs/configuration.md
The default mesos recipe will run mesos::install.
The install recipe installs the specified version of the mesosphere mesos RPM or Debian package and installs it. It’s also configured to stop both mesos-master and mesos-slave init files so that they don't automatically start on server restart.
The master recipe runs mesos::install as well as creating several mesos-master configuration files that are used at startup. This recipe also uses the zookeeper attributes and/or exhibitor attributes to configure the mesos-master using zookeeper. Lastly it sets the mesos-master init config to 'start' so that mesos-master is started on server restart.
The slave recipe runs mesos::install as well as creating several mesos-slave configuration files that are used at startup. This recipe also uses the zookeeper attributes and/or exhibitor attributes to configure the mesos-slave using zookeeper. Lastly it sets the mesos-slave init config to 'start' so that mesos-slave is started on server restart.
The repo recipe contains logic for setting up Mesosphere debian and RPM repositories.
The following cookbooks are dependencies:
The following cookbooks are suggested:
- exhibitor (used for discovering ZooKeeper ensembles via Netflix Exhibitor)
Here is a sample role for configuring a Mesos master in a ZooKeeper backed production mode.
chef_type: role
default_attributes:
description:
env_run_lists:
json_class: Chef::Role
name: mesos_master
override_attributes:
mesos:
version: 1.0.1
master:
flags:
cluster: 'mesos-sandbox'
zk: 'zk://127.0.0.1:2181/mesos'
run_list:
recipe[mesos::master]Here is a sample role for creating a Mesos slave node with a seperate ZooKeeper ensemble dynamically discovered via Netflix Exhibitor:
chef_type: role
default_attributes:
description:
env_run_lists:
json_class: Chef::Role
name: mesos_slave
override_attributes:
mesos:
version: 1.0.1
slave:
flags:
master: 'zk://127.0.0.1:2181/mesos'
run_list:
recipe[mesos::slave]Please see the Contributing and Issue Reporting Guidelines.
- Author: Ray Rodriguez([email protected])
- Author: Robert Veznaver([email protected])
Copyright 2015 Medidata Solutions Worldwide
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.