Hi Robin,
It might be a little late to reply but I thought it would be worth weighing in. Given the Mesos master and slave are primarily configured using command line parameters, the main issue is getting a working install as configuration is fairly simple. It can be quite easy to compile Mesos in your environment if you want to avoid using the publicly available Docker images or apt repositories provoded by Mesosphere (https://www.mesosphere.com/downloads/). Instructions for compiling can be found at http://mesos.apache.org/gettingstarted/. After that you can either use the own configuration management system for deployment or maybe build some appropriate images using tools provided e.g AMIs within EC2. - https://github.com/mdsol/mesos_cookbook - https://github.com/everpeace/cookbook-mesos - https://github.com/deric/puppet-mesos I hope his helps! On Friday, 3 Apr 2015 at 06:43, Robin Anil <[email protected]>, wrote: Fellow Mesos-ers Firstly, I am loving the speed of Mesos so far. I set up a cluster from scratch and have been running docker applications with ease with mesos-dns generating the SRV records. Now I am looking for a serious production setup on AWS I see few choices: 1) Start with linux machines, set up masters, zookeeper and slaves by getting packages from the apt repo 2) Some how use the mesosphere docker images for zookeeper/mesos-master/mesos-slave to bootstrap a cluster. 2) is a lot cleaner but none of the docker images have any sort of help. I have to manually reverse engineer them. Before I invest in building my own docker images and configuration. I wanted to ask if those public docker images are even supported by the community, or if anyone is running a similar setup in production? Experiences/notes will help. Secondly, I am trying to choose between Marathon and Aurora as the scheduler, Aurora has priority and is_production which is very attractive, I would love if some of you can share notes about your experiences with either. Robin
