aboutsummaryrefslogtreecommitdiff
path: root/INSTALL.Linux
diff options
context:
space:
mode:
authorBen Pfaff <blp@nicira.com>2010-08-02 16:04:47 -0700
committerBen Pfaff <blp@nicira.com>2010-08-02 16:04:47 -0700
commit8084a2800f82c6d0ec438cb8f2de24518af2c712 (patch)
tree0f80dee9e74cc5f4664821ba47adc2528d645195 /INSTALL.Linux
parent05d09469058bd78c12bfc60af6093bcbce1901da (diff)
INSTALL.Linux: Improve suggested ovsdb-server invocation.
ovsdb-server should ordinarily connect to managers specified in the database itself, as well as use the SSL configuration specified in the database, but the suggested ovsdb-server command line didn't do that. This commit adds all the relevant arguments that the XenServer integration passes by default. Reported-by: Hao Zheng <hzheng@nicira.com>
Diffstat (limited to 'INSTALL.Linux')
-rw-r--r--INSTALL.Linux13
1 files changed, 10 insertions, 3 deletions
diff --git a/INSTALL.Linux b/INSTALL.Linux
index 7cfba409..3088f8cb 100644
--- a/INSTALL.Linux
+++ b/INSTALL.Linux
@@ -238,9 +238,16 @@ Before starting ovs-vswitchd itself, you need to start its
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
+installation, above, to listen on a Unix domain socket, to connect to
+any managers specified in the database itself, and to use the SSL
+configuration in the database:
+
+ % ovsdb-server /usr/local/etc/ovs-vswitchd.conf.db \
+ --remote=punix:/usr/local/var/run/openvswitch/db.sock \
+ --remote=db:Open_vSwitch,managers \
+ --private-key=db:SSL,private_key \
+ --certificate=db:SSL,certificate \
+ --bootstrap-ca-cert=db:SSL,ca_cert
Then initialize the database using ovs-vsctl. This is only
necessary the first time after you create the database with