[neutron] [all] Networking-ovn and neutron convergence
mnaser at vexxhost.com
Fri Nov 22 16:17:48 UTC 2019
On Fri, Nov 22, 2019 at 10:22 AM Brian Haley <haleyb.dev at gmail.com> wrote:
> For some time we have been discussing in the Neutron community the
> possibility of including the networking-ovn driver  as one of the
> in-tree Neutron drivers. There is already a spec  describing in
> detail why we want to do this and why we think it is good idea. We also
> discussed this during the PTG in Shanghai within our team , and had a
> discussion at the ops-meetup as well .
> The OVN backend is free of many well-known issues which are impacting
> the existing ML2/OVS reference implementation today with the OVS agent.
> For example, OVN provides:
> * Control plane performance optimizations by not using rabbitmq;
> * DVR (and HA) by default, based on OpenFlow so it can be easy offloaded
> e.g. by SmartNICs;
> * Distributed DHCP;
> There are some feature parity gaps when comparing it to ML2/OVS that we
> plan to address. See  for details.
> We think that merging this code into the neutron repository will help to
> grow the networking-ovn community and will help us to keep a healthy
> Neutron team as well by increasing the number or contributors.
> Our current plan is to start merging code from networking-ovn into the
> neutron repository as soon as possible in the Ussuri cycle. But we also
> wanted to get any additional opinions from the wider community about
> this plan. What do users and operators of Neutron think about this?
I'm very much supportive of something like this. The most important thing
is figuring out a proper migration path for those that are sitting on ML2/OVS,
the last time I had a look at this, it wasn't very straightforward AFAIK.
>  https://opendev.org/openstack/networking-ovn
>  https://review.opendev.org/#/c/658414/
>  https://etherpad.openstack.org/p/Shanghai-Neutron-Planning-restored
> Lines 252 - 295
>  https://etherpad.openstack.org/p/shanghai-ptg-ops-meetup
> Lines 62 - 69
> Thanks for any feedback,
> -Brian (and Slawek)
More information about the openstack-discuss