On Wed, Nov 04, 2015 at 02:06:56PM -0800, Karol Mroz wrote: > Hello, > > Support for configuring OVS bridges has been added to our (SUSE) network > manager. > During test (OVS 2.1.2, kernel 3.12.x), a couple things have been uncovered > that > I'd love to get some feedback on. > > 1. OVS bridges appear to report up state, regardless if this is true. For > example, > up is reported even if the underlying bridge port is down, or internally > OVS has > not yet set up the necessary flows to allow for data transmission. Is this > something > that is planned to be addressed? I realize 2.1.2 is an older version, so > perhaps > this has already been addressed in later versions of OVS? > > 2. OVS does not appear to handle hotplugging. For example, if a port, which > is attached > to the an OVS bridge (thus is correctly reflected in ovsdb) arrives on the > system _after_ > the actual `add-port` operation was performed, it will not get enslaved > under the ovs-system > interface. In this case, a manual `del-port/add-port` is needed. Is there > any plan to > add netlink monitoring of interface states (NEWLINK/DELLINK, etc) + > enslavement > when appropriate? >
This has been implemented. Check commit e21c6643a02c6b446d2fbdfde366ea303b4c2730, which is not present in any release yet. Hope that helps. Cascardo. > Thanks! > Karol > _______________________________________________ > dev mailing list > dev@openvswitch.org > http://openvswitch.org/mailman/listinfo/dev _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
