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:
- Marathon: A cluster-wide init and control system for services in cgroups or Docker containers
- Chronos: A fault tolerant job scheduler for Mesos which handles dependencies and ISO8601 based schedules
- Jenkins: An extendable open source continuous integration server
- Storm: A distributed realtime computation system
However since updating mesos to 1.0.0 Chronos, Jenkins and Storm have not been tested and may not be working.
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.
To use this BOSH release, first upload it to your BOSH:
bosh target BOSH_HOST
git clone https://github.com/cloudfoundry-community/mesos-boshrelease.git
cd mesos-boshrelease
bosh upload release releases/mesos/mesos-6.yml
Now create a deployment file (using the files at the templates directory as a starting point).
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
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.
- Fork the project.
- Create a topic branch.
- Implement your feature or bug fix.
- Commit and push your changes.
- Submit a pull request.
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:
---
blobstore:
s3:
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.