None of them are nearly straightforward enough to setup. Here's what I want.
I ask ec2 for a new cloudformation ACMEPaaS stack instance, and I get a url of an admin console back as an output. Behind the scenes, a couple ec2 servers have booted up in my account in a cross-region auto-scaling group. Each is running an instance of the admin webapp and a copy of mesos. I log into the admin webapp, and do some setup stuff like configuring ACLs. There are a couple of utility applications up, such as a private docker image repository, a git server, and an instance of haproxy per server.
I can create stacks in docker and `docker push` them to the private repo. An application is a git repository with a metadata.json in the root (how much ram it needs, how many nodes minimum, how many availability zones, which ports it wants open, what script to run on start, which docker image to run on, etc). I can git push an app to the cluster to do a heroku-esque deploy. The cluster does rolling restarts of my app, and is smart enough to call my health-check script as it goes. Mesos (with cluster state stored in zookeeper) keeps my app running, and schedules it onto the appropriate boxes. When processes or boxes fail, mesos notices, reschedules, and updates haproxy to point to the correct boxes/ports. If I run out of RAM or cpu load hits a threshold, EC2 auto-scaling adds boxes to the cluster, and they're picked up automatically by mesos. I get a text message and an email via Amazon SNS whenever auto-scaling hits. The whole thing has a reasonable API.
I ask ec2 for a new cloudformation ACMEPaaS stack instance, and I get a url of an admin console back as an output. Behind the scenes, a couple ec2 servers have booted up in my account in a cross-region auto-scaling group. Each is running an instance of the admin webapp and a copy of mesos. I log into the admin webapp, and do some setup stuff like configuring ACLs. There are a couple of utility applications up, such as a private docker image repository, a git server, and an instance of haproxy per server.
I can create stacks in docker and `docker push` them to the private repo. An application is a git repository with a metadata.json in the root (how much ram it needs, how many nodes minimum, how many availability zones, which ports it wants open, what script to run on start, which docker image to run on, etc). I can git push an app to the cluster to do a heroku-esque deploy. The cluster does rolling restarts of my app, and is smart enough to call my health-check script as it goes. Mesos (with cluster state stored in zookeeper) keeps my app running, and schedules it onto the appropriate boxes. When processes or boxes fail, mesos notices, reschedules, and updates haproxy to point to the correct boxes/ports. If I run out of RAM or cpu load hits a threshold, EC2 auto-scaling adds boxes to the cluster, and they're picked up automatically by mesos. I get a text message and an email via Amazon SNS whenever auto-scaling hits. The whole thing has a reasonable API.