aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGurucharan Shetty <gshetty@nicira.com>2014-12-12 08:15:46 -0800
committerGurucharan Shetty <gshetty@nicira.com>2014-12-15 09:46:49 -0800
commit7894385af1a9d9ea4a93720dd58492490aa40018 (patch)
tree724c7a4e9709c86daedebb01ec0a494ca4874c77
parentacf72f1322a041fdf30a1c115dbc0e7a6dffac00 (diff)
ovs-docker: Enhance documentation to handle pre-programmed interfaces.
Currently, Controllers and CMSes that integrate with Open vSwitch after following the IntegrationGuide.md, expect to start VMs after the underlying network infrastructure is ready. I have been asked a few times on how to handle the same with containers. This commit provides documentation on one way to achieve it. Signed-off-by: Gurucharan Shetty <gshetty@nicira.com> Acked-by: Thomas Graf <tgraf@noironetworks.com>
-rw-r--r--INSTALL.Docker.md17
1 files changed, 16 insertions, 1 deletions
diff --git a/INSTALL.Docker.md b/INSTALL.Docker.md
index ddbef9955..0086a606a 100644
--- a/INSTALL.Docker.md
+++ b/INSTALL.Docker.md
@@ -76,8 +76,22 @@ and del-port[s] commands.
Once a container interface is added to an Open vSwitch bridge, one can
set VLANs, create Tunnels, add OpenFlow rules etc for more network control.
+Many times, it is important that the underlying network infrastructure is
+plumbed (or programmed) before the application inside the container starts.
+To handle this, one can create a micro-container, attach an Open vSwitch
+interface to that container, set the UUIDS in OVSDB as mentioned in
+[IntegrationGuide.md] and then program the bridge to handle traffic coming out
+of that container. Now, you can start the main container asking it
+to share the network of the micro-container. When your application starts,
+the underlying network infrastructure would be ready. e.g.:
+
+```
+% docker run -d --net=container:$MICROCONTAINER_ID ubuntu:14.04 /bin/sh -c \
+"while true; do echo hello world; sleep 1; done"
+```
+
Please read the man pages of ovs-vsctl, ovs-ofctl, ovs-vswitchd,
-ovsdb-server ovs-vswitchd.conf.db etc for more details.
+ovsdb-server and ovs-vswitchd.conf.db etc for more details about Open vSwitch.
Docker networking is quite flexible and can be used in multiple ways. For more
information, please read:
@@ -89,3 +103,4 @@ Bug Reporting
Please report problems to bugs@openvswitch.org.
[INSTALL.md]:INSTALL.md
+[IntegrationGuide.md]:IntegrationGuide.md