The ovs-sandbox runs in the "dummy mode" by default. In this mode of testing, no packets travel across physical or virtual networks. But sometimes, we may create veth network devices and add them to ovs bridge for developing and testing. It's necessary to add an option.
Signed-off-by: nickcooper-zhangtonghao <[email protected]> --- tutorial/ovs-sandbox | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/tutorial/ovs-sandbox b/tutorial/ovs-sandbox index 4372da4..62f0844 100755 --- a/tutorial/ovs-sandbox +++ b/tutorial/ovs-sandbox @@ -61,6 +61,7 @@ gdb_ovn_controller=false gdb_ovn_controller_ex=false gdb_ovn_controller_vtep=false gdb_ovn_controller_vtep_ex=false +disable_dummy_vswitchd=false builddir= srcdir= schema= @@ -108,6 +109,7 @@ These options force ovs-sandbox to use a particular OVS build: These options force ovs-sandbox to use an installed Open vSwitch: -i, --installed use installed Open vSwitch -g, --gdb-vswitchd run ovs-vswitchd under gdb + -u, --disable-dummy run ovs-vswitchd with disable-dummy mode -d, --gdb-ovsdb run ovsdb-server under gdb --gdb-ovn-northd run ovn-northd under gdb --gdb-ovn-controller run ovn-controller under gdb @@ -154,6 +156,9 @@ EOF gdb_vswitchd=true gdb_vswitchd_ex=false ;; + -u|--disable-dummy) + disable_dummy_vswitchd=true + ;; -e|--gdb-ex-v*) gdb_vswitchd=true gdb_vswitchd_ex=true @@ -360,8 +365,13 @@ fi run ovs-vsctl --no-wait -- init # Start ovs-vswitchd. +ovs_vswitchd_dummy_arg="--enable-dummy=override -vnetdev_dummy" +if $disable_dummy_vswitchd; then + ovs_vswitchd_dummy_arg= +fi + rungdb $gdb_vswitchd $gdb_vswitchd_ex ovs-vswitchd --detach --no-chdir --pidfile -vconsole:off --log-file \ - --enable-dummy=override -vvconn -vnetdev_dummy + -vvconn $ovs_vswitchd_dummy_arg if $ovn; then ovs-vsctl set open . external-ids:system-id=56b18105-5706-46ef-80c4-ff20979ab068 -- 1.8.3.1 _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
