On Sat, Aug 25, 2018 at 11:09:41AM +1200, Brad Cowie wrote: > On 25 August 2018 at 05:38, Ben Pfaff <[email protected]> wrote: > > > On Wed, Aug 22, 2018 at 11:08:02AM +1200, Brad Cowie wrote: > > > I think the right thing to do for netdev_dummy is to default to "up" on > > > dummy ports > > > and the user can admin them down with the ovs-appctl command if they > > want. > > > > Seems reasonable. > > > > This turned out to be more difficult than I expected because of a number > > of bugs. Anyway, I sent a series that fixes the bugs and then changes > > the default behavior: > > https://patchwork.ozlabs.org/project/openvswitch/list/? > > series=62396 > > > I tried the ovs faucet tutorial as written against faucet@master and > this patch series + https://patchwork.ozlabs.org/patch/962002/ and > everything seems to be working again. Big thanks!
That's good news, thanks for testing! > So I think what I will do now is spend some time this week writing a > patch against the ovs faucet tutorial recommending using OVS <=2.8 for > now until this patch is merged and released (as OVS 2.10.1? 2.11? not > sure where you will merge to). In the past 2 weeks we've made some > huge improvements to the faucet pipeline so the output of the tutorial > is slightly wrong now anyway. I guess it will likely go in 2.11. I'm a little sad that it's been broken so long but that's my fault so I can't complain too much. > By the way we can dynamically generate our openflow pipeline now such > that tables are automatically sized (more important for real hardware) > and disable tables that aren't used (e.g. FIB tables are now turned > off when routing disabled, ACL tables disabled when no ACLs have been > applied). We are mostly doing this by sending a OFPMP_TABLE_FEATURES > packet with the tables and matches we wish to use in each (we also > include a name for each table which I see OVS 2.10.0 now > supports). However we haven't been able to get OVS to successfully > parse our OFPMP_TABLE_FEATURES packet yet. I guess I should open a new > thread on ovs-dev to discuss whether OVS actually supports this or > not? So far, OVS provides a pretty bare OFPMP_TABLE_FEATURES implementation, which allows a controller to query the features that it supports. It provides very little (maybe nothing?) in terms of allowing a controller to modify the features supported. That's primarily because OVS is mainly a software implementation where we can support all the features all the time. The motivation for OFPMP_TABLE_FEATURES when it was added to the OpenFlow specs was to allow a controller to configure hardware features that offer trade-offs. OVS does of course run on some hardware switches; I don't know whether the vendors who customize it for their hardware add support for OFPMP_TABLE_FEATURES so that it can configure trade-offs, though I suspect they do not. I'm happy to discuss this here or on ovs-dev. _______________________________________________ discuss mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
