Otherwise ovs-vswitchd can't immediately start working (until some other
call to ovs-vsctl initializes the database). This is most obvious if one
runs "ovs-vsctl list Open_vSwitch ." as the first command, because the
output will not show the changes that ovs-vswitchd will make to the
database at startup (in particular initializing datapath_types and
iface_types), which is confusing.
Signed-off-by: Ben Pfaff <b...@nicira.com>
---
tutorial/ovs-sandbox | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/tutorial/ovs-sandbox b/tutorial/ovs-sandbox
index 1504ea9..9520a41 100755
--- a/tutorial/ovs-sandbox
+++ b/tutorial/ovs-sandbox
@@ -1,6 +1,6 @@
#! /bin/sh
#
-# Copyright (c) 2013 Nicira, Inc.
+# Copyright (c) 2013, 2015 Nicira, Inc.
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
@@ -235,6 +235,9 @@ run ovsdb-tool create conf.db "$schema"
rungdb $gdb_ovsdb ovsdb-server --detach --no-chdir --pidfile -vconsole:off
--log-file \
--remote=punix:"$sandbox"/db.sock
+# Initialize database.
+run ovs-vsctl --no-wait -- init
+
# Start ovs-vswitchd.
rungdb $gdb_vswitchd ovs-vswitchd --detach --no-chdir --pidfile -vconsole:off
--log-file \
--enable-dummy=override -vvconn -vnetdev_dummy
--
2.1.3
_______________________________________________
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev
