Guest24897
/
DockerCLI
mirror of https://github.com/docker/cli.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Put the network UI and overlay docs in separate files 

.. and link to them separately. They are different features.

Signed-off-by: Michael Bridgen <mikeb@squaremobius.net>
This commit is contained in:
Michael Bridgen 2015-06-30 09:13:45 +01:00 committed by Tibor Vass
parent e1b8ab477e
commit 82de777c9d
3 changed files with 16 additions and 16 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
experimental/README.md
View File

@ -64,7 +64,8 @@ After downloading the appropriate binary, you can follow the instructions
* [Support for Docker plugins](plugins.md) * [Support for Docker plugins](plugins.md)
* [Volume plugins](plugins_volume.md) * [Volume plugins](plugins_volume.md)
* [Network plugins](plugins_network.md) * [Network plugins](plugins_network.md)
* [Native Multi-host networking](networking.md) * [Networking and Services UI](networking.md)
* [Native multi-host networking](network_overlay.md)
* [Compose, Swarm and networking integration](compose_swarm_networking.md) * [Compose, Swarm and networking integration](compose_swarm_networking.md)
## How to comment on an experimental feature ## How to comment on an experimental feature

14
experimental/network_overlay.md Normal file
View File

@ -0,0 +1,14 @@
# Native Multi-host networking
There is a lot to talk about the native multi-host networking and the `overlay` driver that makes it happen. The technical details are documented under https://github.com/docker/libnetwork/blob/master/docs/overlay.md.
Using the above experimental UI `docker network`, `docker service` and `--publish-service`, the user can exercise the power of multi-host networking.
Since `network` and `service` objects are globally significant, this feature requires distributed states provided by the `libkv` project.
Using `libkv`, the user can plug any of the supported Key-Value store (such as consul, etcd or zookeeper).
User can specify the Key-Value store of choice using the `--kv-store` daemon flag, which takes configuration value of format `PROVIDER:URL`, where
`PROVIDER` is the name of the Key-Value store (such as consul, etcd or zookeeper) and
`URL` is the url to reach the Key-Value store.
Example : `docker -d --kv-store=consul:localhost:8500`
Send us feedback and comments on [#14083](https://github.com/docker/docker/issues/14083)
or on the usual Google Groups (docker-user, docker-dev) and IRC channels.

15
experimental/networking.md
View File

@ -116,20 +116,5 @@ To remove the a service:
$ docker service detach a0ebc12d3e48 my-service.foo $ docker service detach a0ebc12d3e48 my-service.foo
$ docker service unpublish my-service.foo $ docker service unpublish my-service.foo
## Native Multi-host networking
There is a lot to talk about the native multi-host networking and the `overlay` driver that makes it happen. The technical details are documented under https://github.com/docker/libnetwork/blob/master/docs/overlay.md.
Using the above experimental UI `docker network`, `docker service` and `--publish-service`, the user can exercise the power of multi-host networking.
Since `network` and `service` objects are globally significant, this feature requires distributed states provided by the `libkv` project.
Using `libkv`, the user can plug any of the supported Key-Value store (such as consul, etcd or zookeeper).
User can specify the Key-Value store of choice using the `--kv-store` daemon flag, which takes configuration value of format `PROVIDER:URL`, where
`PROVIDER` is the name of the Key-Value store (such as consul, etcd or zookeeper) and
`URL` is the url to reach the Key-Value store.
Example : `docker -d --kv-store=consul:localhost:8500`
Send us feedback and comments on [#14083](https://github.com/docker/docker/issues/14083) Send us feedback and comments on [#14083](https://github.com/docker/docker/issues/14083)
or on the usual Google Groups (docker-user, docker-dev) and IRC channels. or on the usual Google Groups (docker-user, docker-dev) and IRC channels.