Bug#781918: RFP: docker-swarm -- Docker-native clustering system
Package: wnpp
Severity: wishlist
* Package name : docker-swarm
Version : 0.2.0-rc2 (for experimental)
Upstream Author : Victor Vieux <vieux@docker.com> & Andrea Luzzardi
Copyright holder: Docker, Inc.
* URL : https://docs.docker.com/swarm/ https://github.com/docker/swarm
* License : Apache 2.0 (documentation under Creative Commons - unsure of full terms)
Programming Lang: Go
Description : Docker-native clustering system
Docker Swarm is native clustering for Docker. It turns a pool of Docker
hosts into a single, virtual host.
Swarm serves the standard Docker API, so any tool which already communicates
with a Docker daemon can use Swarm to transparently scale to multiple hosts:
Dokku, Compose, Krane, Flynn, Deis, DockerUI, Shipyard, Drone, Jenkins...
and, of course, the Docker client itself.
Like other Docker projects, Swarm follows the "batteries included but
removable" principle. It ships with a set of simple scheduling backends out
of the box, and as initial development settles, an API will be developed to
enable pluggable backends. The goal is to provide a smooth out-of-the-box
experience for simple use cases, and allow swapping in more powerful backends,
like Mesos, for large scale production deployments.
More about Docker Swarm:
The goal of Docker Swarm is to enable easier management of several Docker
systems -- many people looking to use docker (see docker.io package) in
production would benefit from this. At the moment, the proposed installation
instructions are to run Swarm as a Docker image, but this requires running
potentially untrusted code obtained over the Internet.
It is not a dependency for any other package. There are many competing
technologies but this is the most popular open source one, since it is
part of the Docker ecosystem itself.
I do not use it, yet, however many others do (or are looking to trial it).
Proposed maintainers for this package:
The Debian Golang team seems like an appropriate place to host this work.
As this is an RFP and not an ITP, I hope they are willing to maintain it.
Reply to: