|
1 | | -# Swarm: a Docker-native clustering system |
| 1 | +# Classic Swarm: a Docker-native clustering system |
2 | 2 |
|
3 | 3 | [](https://godoc.org/github.com/docker/swarm) |
4 | | -[](https://jenkins.dockerproject.org/view/Swarm/job/Swarm%20Master/) |
5 | 4 | [](https://travis-ci.org/docker/swarm) |
6 | 5 | [](https://goreportcard.com/report/github.com/docker/swarm) |
7 | 6 |
|
8 | 7 |  |
9 | 8 |
|
10 | | -Docker Swarm is native clustering for Docker. It turns a pool of Docker hosts |
| 9 | +Docker Swarm "Classic" is native clustering for Docker. It turns a pool of Docker hosts |
11 | 10 | into a single, virtual host. |
12 | 11 |
|
13 | 12 | ## Swarm Disambiguation |
14 | 13 |
|
15 | | -**Docker Swarm standalone**: This project. A native clustering system for |
| 14 | +**Docker Swarm "Classic" standalone**: This project. A native clustering system for |
16 | 15 | Docker. It turns a pool of Docker hosts into a single, virtual host using an |
17 | 16 | API proxy system. See [Docker Swarm overview](https://docs.docker.com/swarm/overview/). |
18 | | -It is Docker's first container orchestration project that began in 2014. |
19 | | -Combined with Docker Compose, it's a very convenient tool to schedule containers. |
20 | | -Its flexibility and simplicity make it easy to integrate with existing IT infrastructure. |
21 | | -Many companies and users have deployed Docker Swarm standalone for production and experimental |
22 | | -projects. Docker does not currently have a plan to deprecate Docker Swarm. |
23 | | -The Docker API is backward compatible so Docker Swarm will continue to work with |
24 | | -future Docker Engine versions. |
| 17 | +It was Docker's first container orchestration project that began in 2014. |
25 | 18 |
|
26 | 19 | **[Swarmkit](https://github.com/docker/swarmkit)**: Cluster |
27 | 20 | management and orchestration features in Docker Engine 1.12 or later. When Swarmkit |
28 | 21 | is enabled we call Docker Engine running in swarm mode. See the |
29 | 22 | feature list: [Swarm mode overview](https://docs.docker.com/engine/swarm/). |
30 | 23 | This project focuses on micro-service architecture. It supports service |
31 | 24 | reconciliation, load balancing, service discovery, built-in certificate rotation, etc. |
32 | | -Swarm mode is Docker's response to the community's request to simplify service orchestration. |
33 | | - |
34 | | -While the 2 projects may accomplish similar tasks, they work on different levels |
35 | | -in terms of service architecture. Users can choose which one is more suitable for their workload. |
36 | | -If you're in doubt, Docker recommends that you try Docker 1.12 and later with built-in swarm mode. |
37 | | - |
38 | | -## Docker Swarm standalone |
39 | | - |
40 | | -Swarm serves the standard Docker API, so any tool which already communicates |
41 | | -with a Docker daemon can use Swarm to transparently scale to multiple hosts: |
42 | | -Dokku, Compose, Krane, Flynn, Deis, DockerUI, Shipyard, Drone, Jenkins... and, |
43 | | -of course, the Docker client itself. |
44 | | - |
45 | | -Like other Docker projects, Swarm follows the "batteries included but removable" |
46 | | -principle. It ships with a set of simple scheduling backends out of the box, and |
47 | | -as initial development settles, an API will be developed to enable pluggable |
48 | | -backends. The goal is to provide a smooth out-of-the-box experience for simple |
49 | | -use cases, and allow swapping in more powerful backends, like Mesos, for large |
50 | | -scale production deployments. |
51 | | - |
52 | | -## Installation for Swarm Users |
53 | | - |
54 | | -For instructions on using Swarm in your dev, test or production environment, refer to the Docker Swarm documentation on [docs.docker.com](http://docs.docker.com/swarm/). |
55 | | - |
56 | | -## Building Swarm from Source |
57 | | - |
58 | | -To compile Swarm from source code, refer to the instructions in [CONTRIBUTING.md](http://github.com/docker/swarm/blob/master/CONTRIBUTING.md) |
59 | | - |
60 | | -## Participating |
61 | | - |
62 | | -You can contribute to Docker Swarm in several different ways: |
63 | | - |
64 | | - - If you have comments, questions, or want to use your knowledge to help others, come join the conversation on IRC. You can reach us at #docker-swarm on Freenode. |
65 | | - |
66 | | - - To report a problem or request a feature, please file an issue. |
67 | | - |
68 | | - - Of course, we welcome pull requests and patches. Setting up a local Swarm development environment and submitting PRs is described [here](http://github.com/docker/swarm/blob/master/CONTRIBUTING.md). |
69 | | - |
70 | | -Finally, if you want to see what we have for the future and learn more about our release cycles, all this information is detailed on the [wiki](https://github.com/docker/swarm/wiki) |
71 | 25 |
|
72 | 26 | ## Copyright and license |
73 | 27 |
|
|
0 commit comments