I'm not aware of any issues. Perhaps you can propose a patch to just change the default in Neutron to that interface and people can -1 if there are any concerns.
On Tue, Mar 29, 2016 at 4:32 PM, Inessa Vasilevskaya < ivasilevsk...@mirantis.com> wrote: > Hi all, > > I spent some time researching the current state of native ovsdb interface > feature, which has been fully implemented and merged since Liberty [1][2]. > I was pretty much impressed by the expected performance improvement (as per > spec [1], some interesting research on ovs-vsctl + rootwrap also done here > [3]). Preliminary test results also showed that native interface does quite > well. > > So my question is - why don’t we make native interface the default option > for voting gate jobs? Are there any caveats or security issues that I am > unaware of? > > Regards, > > Inessa > > [1] > https://specs.openstack.org/openstack/neutron-specs/specs/kilo/vsctl-to-ovsdb.html > > [2] https://blueprints.launchpad.net/neutron/+spec/vsctl-to-ovsd > <https://blueprints.launchpad.net/neutron/+spec/vsctl-to-ovsdb> > [3] > http://blog.otherwiseguy.com/replacing-ovs-vsctl-calls-with-native-ovsdb-in-neutron/ > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
