It's not quite clear reading the chronos doc:

https://mesos.github.io/chronos/docs/api.html#adding-a-docker-job

Mesos 0.22.0 added support for forcibly pulling the latest version of your Docker image before launching the task, and this behavior can be enabled in Chronos by adding the forcePullImage boolean to your container configuration.

Chronos will default to not doing a `docker pu

Replace concrete Bastion Executor with Agnostik.
So everyone can use whatever they want as guarantee.

I don't want to use current chunks loop for replication (mostly because is still unclear how it works).
What I would like is to set our cluster to replicate as much chunks as possible up to REPLICATION_BANDWIDTH_LIMIT_KBPS

What should I have to set and how ? I think that both REPLICATION_BANDWIDTH_LIMIT_KBPS and chunks loop limits are honored, so I have to set chunk loop to very high value

I'm confused about the example for data migration during code updates. The runMigration example function asserts that this is an upgrade from version 0 to version 1. Shouldn't this be from version 1 to version 2? Or am I completely misunderstanding how migrations work?

infinit user pull       
Remotely deleted identity for user "bushbaby123".

not sure if it actually deleted the user, but this does not sound correct

v0.8.0

In the API HTML documentation: The example urls currently have the .erl suffix. This needs to change to a .json suffix and example request/response data should be added below.

The Quickstart (in HTML/Markdown) needs to be updated, the Java tutorial, and possibly the FAQ.

The file src/service_api/README.markdown needs to be updated.

Hey guys, really enjoying using this project.

Noticed you built a Slack integration in this PR: Add slack notification #21

It would be fantastic if the README details how I might be able to wire up Chaos Lambda running on my AWS account with my Slack. Any thoughts on how soon this can get done?

Is the documentation of metronome hosted somewhere? I am validating it against other options to use it for making a microservice to schedule distributed tasks. With the documentation it would be easy for me to access its capabilities.