vbatts/pkg
1
0
Fork 0
Code Pull requests Releases Activity
pkg/discovery
History
Victor Vieux cc9d62dd28 Before that change, etcd and zookeeper would fail to instantiate 
the discovery without the key being already there in the store or
created beforehand and implicitely by a 'swarm join'.

Signed-off-by: Alexandre Beslic <abronan@docker.com>
Signed-off-by: Victor Vieux <vieux@docker.com>

This PR allows to configure the discovery path using the
--discovery-opt flag (with "kv.path=path/to/nodes"). We
can point to "docker/nodes" and use the docker discovery.

If docker instances are advertising to the cluster using
the `--cluster-advertise` flag, the swarm join command
becomes unnecessary.

Signed-off-by: Alexandre Beslic <abronan@docker.com>
Signed-off-by: Victor Vieux <vieux@docker.com>
2016-01-06 05:18:52 -08:00
..
file Add TLS support for discovery backend 2015-10-07 16:01:00 -07:00
kv Before that change, etcd and zookeeper would fail to instantiate 2016-01-06 05:18:52 -08:00
nodes Add TLS support for discovery backend 2015-10-07 16:01:00 -07:00
backends.go Enhancing --cluster-advertise to support <interface-name> 2015-10-27 11:03:22 -07:00
discovery.go Add TLS support for discovery backend 2015-10-07 16:01:00 -07:00
discovery_test.go remove testify asserts from pkg/discovery 2015-10-02 13:05:15 -07:00
entry.go Add pkg/discovery for nodes discovery 2015-09-25 13:33:23 -07:00
generator.go Add pkg/discovery for nodes discovery 2015-09-25 13:33:23 -07:00
generator_test.go remove testify asserts from pkg/discovery 2015-10-02 13:05:15 -07:00
README.md fix discovery package documentation with the right --cluster* flags 2015-09-27 13:40:42 -07:00

README.md

page_title page_description page_keywords
Docker discovery discovery docker, clustering, discovery

Discovery

Docker comes with multiple Discovery backends.

Backends

Using etcd

Point your Docker Engine instances to a common etcd instance. You can specify the address Docker uses to advertise the node using the --cluster-advertise flag.

$ docker daemon -H=<node_ip:2376> --cluster-advertise=<node_ip:2376> --cluster-store etcd://<etcd_ip1>,<etcd_ip2>/<path>

Using consul

Point your Docker Engine instances to a common Consul instance. You can specify the address Docker uses to advertise the node using the --cluster-advertise flag.

$ docker daemon -H=<node_ip:2376> --cluster-advertise=<node_ip:2376> --cluster-store consul://<consul_ip>/<path>

Using zookeeper

Point your Docker Engine instances to a common Zookeeper instance. You can specify the address Docker uses to advertise the node using the --cluster-advertise flag.

$ docker daemon -H=<node_ip:2376> --cluster-advertise=<node_ip:2376> --cluster-store zk://<zk_addr1>,<zk_addr2>/<path>