Docker Clustering: Design proposal.

Authors: @aluzzardi and @vieux.

[![ScreenShot](http://cl.ly/image/2j0S0Y3h0y3o/Screen%20Shot%202014-10-30%20at%2017.23.38.png)](https://www.youtube.com/watch?v=vtnSL79rZ6o)

The goal and scope of this change is to allow docker to manage a cluster
of docker hosts.

The target audience for clustering is modeled after Docker itself:
developer and devops first then enterprise later. Enterprise requires
additional features such as authentication, ACLs, auditing and tooling
which will come at a later time.

The system is designed to handle workloads in the same way as Docker: it
can run both long-running and one-off tasks. Batch processing can be
built on top of the API using the one-off primitive.

The architecture is based on an evented model where the master queries
the registered slaves within the system and checks the current state of
the slaves against the requested state by the user.  It reconciles any
differences and updates the cluster state with the required changes.

Signed-off-by: Andrea Luzzardi <aluzzardi@gmail.com>
Signed-off-by: Victor Vieux <vieux@docker.com>
How would this work with docker run --restart policy?

If I set docker run --restart=on-failure:3 , the node by itself will restart (max: 3 times) if the container exits with a non-zero exit code. So master rebalancing will only work after the 3rd time? Or will only work if I set it to default --restart=no ?