diff options
| author | Ben Pfaff <blp@nicira.com> | 2010-06-18 15:58:13 -0700 |
|---|---|---|
| committer | Ben Pfaff <blp@nicira.com> | 2010-06-23 09:54:14 -0700 |
| commit | cb8141b2334a54d45bddefda3bf537f2907eec7b (patch) | |
| tree | b318830d91fdfdb75ba12824ebc4fc859d7153cb /INSTALL.Linux | |
| parent | 254604d84b48fde8e19299a10be7145adee52f98 (diff) | |
Better document how ovsdb-server is meant to be used.
DarkBls <darkbls@yahoo.com> had the idea that a single ovsdb-server could
be used to serve configuration details across the network to multiple
remote ovs-vswitchd instances. This doesn't work, but the documentation
didn't spell it out. This commit should help.
Diffstat (limited to 'INSTALL.Linux')
| -rw-r--r-- | INSTALL.Linux | 7 |
1 files changed, 4 insertions, 3 deletions
diff --git a/INSTALL.Linux b/INSTALL.Linux index bd7038c8..b4f9b767 100644 --- a/INSTALL.Linux +++ b/INSTALL.Linux @@ -229,9 +229,10 @@ Startup ======= Before starting ovs-vswitchd itself, you need to start its -configuration database, ovsdb-server. Configure it to use the -database you created during step 7 of installation, above, and to -listen on a Unix domain socket, e.g.: +configuration database, ovsdb-server. Each machine on which Open +vSwitch is installed should run its own copy of ovsdb-server. +Configure it to use the database you created during step 7 of +installation, above, and to listen on a Unix domain socket, e.g.: % ovsdb-server /usr/local/etc/ovs-vswitchd.conf.db --remote=punix:/usr/local/var/run/openvswitch/db.sock |