Merge pull request #14278 from squaremo/separate_overlay_docs

Put the network UI and overlay docs in separate files

experimental/README.md

@@ -64,7 +64,8 @@ After downloading the appropriate binary, you can follow the instructions
 * [Support for Docker plugins](plugins.md)
 * [Volume plugins](plugins_volume.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)
 
 ## How to comment on an experimental feature

experimental/network_overlay.md

@@ -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.

experimental/networking.md

@@ -116,20 +116,5 @@ To remove the a service:
         $ docker service detach a0ebc12d3e48 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)
 or on the usual Google Groups (docker-user, docker-dev) and IRC channels.
-