Hi Flavio,
I tried to look closer into ifup-ovs script particularly for OVSDPDKPort &
OVSDPDKBOND cases.
With the change given below (git diff) at the end OVSDPDKBOND case, I see that
the routes
are getting installed again after adding dpdkbond port to the bridge. Perhaps
the same fix
needs to be done for OVSDPDKPort case as well. I think we need to invoke
$OTHERSCRIPT
(ifup-eth) for the bridge in each of the above cases.
Does this fix in ifup-ovs script makes sense ? If you agree, I will post a
patch for review on
ovs-dev list.
----
diff --git a/rhel/etc_sysconfig_network-scripts_ifup-ovs
b/rhel/etc_sysconfig_network-scripts_ifup-ovs
index b95220a..132ed29 100755
--- a/rhel/etc_sysconfig_network-scripts_ifup-ovs
+++ b/rhel/etc_sysconfig_network-scripts_ifup-ovs
@@ -202,6 +202,7 @@ case "$TYPE" in
ovs-vsctl -t ${TIMEOUT} \
-- --if-exists del-port "$OVS_BRIDGE" "$DEVICE" \
-- add-bond "$OVS_BRIDGE" "$DEVICE" ${BOND_IFACES}
$OVS_OPTIONS ${IFACE_TYPES} ${OVS_EXTRA+-- $OVS_EXTRA}
+ ${OTHERSCRIPT} $OVS_BRIDGE
;;
*)
echo $"Invalid OVS interface type $TYPE"
----
_______________________________________________
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
