Apache Mesos BOSH release
Latest commit 367888b Aug 1, 2015 @frodenas frodenas Mesos Bosh release v4
Failed to load latest commit information.
examples Add bosh-lite deployment manifest Aug 1, 2015
jobs Remove setting the hostname Aug 1, 2015
packages Add storm package Jul 29, 2015
releases Mesos Bosh release v4 Aug 1, 2015
src Fix hostname, private and public ip Jul 27, 2015
.gitattributes Initial import Mar 3, 2014
.gitignore Use new release format Jul 22, 2015
LICENSE Initial import Mar 3, 2014
README.md Mesos Bosh release v4 Aug 1, 2015


Bosh release for Apache Mesos

One of the fastest ways to get Apache Mesos running on any infrastructure is to deploy this BOSH release.

This BOSH release includes the following Apache Mesos frameworks:

  • Chronos: A fault tolerant job scheduler for Mesos which handles dependencies and ISO8601 based schedules
  • Marathon: A cluster-wide init and control system for services in cgroups or Docker containers
  • Jenkins: An extendable open source continuous integration server
  • Storm: A distributed realtime computation system


This is not presently a production ready Apache Mesos BOSH release. This is a work in progress. It is suitable for experimentation and may not become supported in the future.


Upload the BOSH release

To use this BOSH release, first upload it to your BOSH:

bosh target BOSH_HOST
git clone https://github.com/cf-platform-eng/mesos-boshrelease.git
cd mesos-boshrelease
bosh upload release releases/mesos/mesos-4.yml

Create a BOSH deployment manifest

Now create a deployment file (using the files at the examples directory as a starting point).

Deploy using the BOSH deployment manifest

Using the previous created deployment manifest, now we can deploy it:

bosh deployment path/to/deployment.yml
bosh -n deploy


In the spirit of free software, everyone is encouraged to help improve this project.

Here are some ways you can contribute:

  • by using alpha, beta, and prerelease versions
  • by reporting bugs
  • by suggesting new features
  • by writing or editing documentation
  • by writing specifications
  • by writing code (no patch is too small: fix typos, add comments, clean up inconsistent whitespace)
  • by refactoring code
  • by closing issues
  • by reviewing patches

Submitting an Issue

We use the GitHub issue tracker to track bugs and features. Before submitting a bug report or feature request, check to make sure it hasn't already been submitted. You can indicate support for an existing issue by voting it up. When submitting a bug report, please include a Gist that includes a stack trace and any details that may be necessary to reproduce the bug, including your gem version, Ruby version, and operating system. Ideally, a bug report should include a pull request with failing specs.

Submitting a Pull Request

  1. Fork the project.
  2. Create a topic branch.
  3. Implement your feature or bug fix.
  4. Commit and push your changes.
  5. Submit a pull request.

Create new release

Creating new final release

To create a new final release you need to get read/write API credentials to the @cloudfoundry-community s3 account.

Please email Dr Nic Williams and he will create unique API credentials for you.

Create a config/private.yml file with the following contents:

    access_key_id:     ACCESS
    secret_access_key: PRIVATE

You can now create final releases for everyone to enjoy!

bosh create release
# test this dev release
git commit -m "updated mesos"
bosh create release --final
git commit -m "creating vXYZ release"
git tag vXYZ
git push origin master --tags


See LICENSE for details. Copyright (c) 2014-2015 Pivotal Software, Inc.