Comment 1 for bug 1744829

Lujin Luo,

Thanks for filing this bug. Per our conversation in IRC of moments ago, while we need to fix the specific buggy code introduced by https://review.openstack.org/#/c/407868, we also need to think about some follow up questions:

1) Is it better for our users a ML2 plugin with OVO for port bindings and old engine facade than the one we had before with new engine facade and old style DB code?

2) In the longer term, does this mean that every time we adopt OVO in a piece of code, we are going to undo the good work done in adopting the new engine facade?

Both OVO and the new engine facade are good things that we certainly want to adopt in Neutron. We are painting ourselves into a corner where we have to choose between one or the other. I pinged Matt Riedemann earlier today and asked him about Nova's adoption of new engine facade and OVO. It is complete and they co-exist nicely. This event should prompt us to think how we can get Neutron in the same position. I think this should be a topic that we discuss in Dublin and put together a solid plan to move ahead with both OVO and new engine facade