mirror of https://github.com/docker/docs.git
Tweak docs introduction
A bit punchier and tweaked the formatting to make it consistent with other docs/projects. Signed-off-by: Ben Firshman <ben@firshman.co.uk>
This commit is contained in:
parent
f5205cb7ca
commit
4b48b68514
22
README.md
22
README.md
|
|
@ -2,18 +2,20 @@
|
||||||
|
|
||||||

|

|
||||||
|
|
||||||
`swarm` is a simple tool which controls a cluster of Docker hosts and exposes it
|
Docker Swarm is native clustering for Docker. It turns a pool of Docker hosts
|
||||||
as a single "virtual" host.
|
into a single, virtual host.
|
||||||
|
|
||||||
`swarm` uses the standard Docker API as its frontend, which means any tool which
|
Swarm serves the standard Docker API, so any tool which already communicates
|
||||||
speaks Docker can control swarm transparently: dokku, fig, krane, flynn, deis,
|
with a Docker daemon can use Swarm to transparently scale to multiple hosts:
|
||||||
docker-ui, shipyard, drone.io, Jenkins... and of course the Docker client itself.
|
Dokku, Compose, Krane, Flynn, Deis, DockerUI, Shipyard, Drone, Jenkins... and,
|
||||||
|
of course, the Docker client itself.
|
||||||
|
|
||||||
Like the other Docker projects, `swarm` follows the "batteries included but removable"
|
Like other Docker projects, Swarm follows the "batteries included but removable"
|
||||||
principle. It ships with a simple scheduling backend out of the box, and as initial
|
principle. It ships with a simple scheduling backend out of the box, and as
|
||||||
development settles, an API will develop to enable pluggable backends. The goal is
|
initial development settles, an API will develop to enable pluggable backends.
|
||||||
to provide a smooth out-of-box experience for simple use cases, and allow swapping
|
The goal is to provide a smooth out-of-box experience for simple use cases, and
|
||||||
in more powerful backends, like `Mesos`, for large scale production deployments.
|
allow swapping in more powerful backends, like Mesos, for large scale production
|
||||||
|
deployments.
|
||||||
|
|
||||||
## Installation
|
## Installation
|
||||||
|
|
||||||
|
|
|
||||||
25
userguide.md
25
userguide.md
|
|
@ -4,21 +4,22 @@ page_description: Swarm: a Docker-native clustering system
|
||||||
page_keywords: docker, swarm, clustering
|
page_keywords: docker, swarm, clustering
|
||||||
---
|
---
|
||||||
|
|
||||||
# Docker Swarm: a Docker-native clustering system
|
# Docker Swarm
|
||||||
|
|
||||||
Docker `swarm` helps you control a cluster of Docker hosts (known as nodes)
|
Docker Swarm is native clustering for Docker. It turns a pool of Docker hosts
|
||||||
and expose them as a single "virtual" host.
|
into a single, virtual host.
|
||||||
|
|
||||||
The Docker `swarm` manager can be interacted with using the Docker API, which means
|
Swarm serves the standard Docker API, so any tool which already communicates
|
||||||
any tool which can communicate with a Docker Daemon using that API, can control
|
with a Docker daemon can use Swarm to transparently scale to multiple hosts:
|
||||||
a Docker swarm transparently: dokku, fig, krane, flynn, deis, docker-ui, shipyard,
|
Dokku, Compose, Krane, Flynn, Deis, DockerUI, Shipyard, Drone, Jenkins... and,
|
||||||
drone.io, Jenkins... and of course the Docker client itself.
|
of course, the Docker client itself.
|
||||||
|
|
||||||
Like the other Docker projects, `swarm` follows the "batteries included but removable"
|
Like other Docker projects, Swarm follows the "batteries included but removable"
|
||||||
principle. It ships with a simple scheduling backend out of the box, and as initial
|
principle. It ships with a simple scheduling backend out of the box, and as
|
||||||
development settles, an API will develop to enable pluggable backends. The goal is
|
initial development settles, an API will develop to enable pluggable backends.
|
||||||
to provide a smooth out-of-box experience for simple use cases, and allow swapping
|
The goal is to provide a smooth out-of-box experience for simple use cases, and
|
||||||
in more powerful backends, like `Mesos`, for large scale production deployments.
|
allow swapping in more powerful backends, like Mesos, for large scale production
|
||||||
|
deployments.
|
||||||
|
|
||||||
## Installation
|
## Installation
|
||||||
|
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue