bump versions to Mesos 0.20.0, Marathon 0.8.0.

README.md

@@ -2,7 +2,7 @@
 
 Spin up your [Mesos](http://mesos.apache.org) Cluster with [Vagrant](http://www.vagrantup.com)! (Both Virtualbox and AWS are supported.)
 
-This spins up Mesos 0.20.1 cluster and also spins up a framework server node in which [Marathon](https://github.com/mesosphere/marathon) (0.7.1) and [Chronos](http://github.com/mesos/chronos) (2.1.0) are runinng.  This means you can build your own __Mesos+Marathon+Chronos+Docker__ PaaS with `vagrant up`!!  Marathon works as distributed `init.d` and Chronos works as distributed `cron`!!  _If you wanted to deploy docker containers, please refer to the chapter "Deploy Docker Container with Marathon" in [thig blog entry](http://frankhinek.com/deploy-docker-containers-on-mesos-0-20/)._
+This spins up Mesos 0.21.0 cluster and also spins up a framework server node in which [Marathon](https://github.com/mesosphere/marathon) (0.8.0) and [Chronos](http://github.com/mesos/chronos) (2.1.0) are runinng.  This means you can build your own __Mesos+Marathon+Chronos+Docker__ PaaS with `vagrant up`!!  Marathon works as distributed `init.d` and Chronos works as distributed `cron`!!  _If you wanted to deploy docker containers, please refer to the chapter "Deploy Docker Container with Marathon" in [thig blog entry](http://frankhinek.com/deploy-docker-containers-on-mesos-0-20/)._
 
 * Using VirtualBox
 	* [Mesos Standalone on VirtualBox](#svb)

multinodes/cluster.yml

@@ -1,5 +1,5 @@
 # Mesos cluster configurations
-mesos_version: "0.20.1"
+mesos_version: "0.21.0"
 
 # The numbers of servers
 ##############################

standalone/Vagrantfile

@@ -3,7 +3,7 @@
 # vagrant plugins required:
 # vagrant-berkshelf, vagrant-omnibus, vagrant-hosts
 require 'yaml'
-mesos_version = "0.20.1"
+mesos_version = "0.21.0"
 
 Vagrant.configure("2") do |config|
   # https://vagrantcloud.com/everpeace/boxes/mesos