[openstack-dev] [neutron] neutron-lib impact

Gary Kotton gkotton at vmware.com
Wed Nov 16 08:55:53 UTC 2016

The directory integration will break all of the plugins and neutron projects. I do not think that this is something that we should do. It breaks the neutron API contract.
I think that we should only unblock the patch https://review.openstack.org/#/c/386845. I think that due to the fact that this patch (very big) will break all plugins, we should only approve it once every sub project owner has chimed in. This will mean that she/he will need to understand that there may be some tweaks involved in getting unit tests to pass. CI may automagically work.
I feel that as a core reviewer my responsibility is to make sure that we do not break things. In addition to this we have a responsibility to ensure that things continue to work. Hopefully we can find a way to do this in a more friendly manner.

From: "Armando M." <armamig at gmail.com>
Reply-To: OpenStack List <openstack-dev at lists.openstack.org>
Date: Wednesday, November 16, 2016 at 6:51 AM
To: OpenStack List <openstack-dev at lists.openstack.org>
Subject: [openstack-dev] [neutron] neutron-lib impact

Hi neutrinos,

As mentioned during the last team meeting [1], there is a change [2] in the works aimed at adopting the neutron plugins directory as provided in neutron-lib 1.0.0 [3].

As shown in [2], the switch to using the directory is relatively straightforward. I leave the rest of the affected repos as an exercise for the reader :)


[1] http://eavesdrop.openstack.org/meetings/networking/2016/networking.2016-11-14-21.00.txt
[2] https://review.openstack.org/#/q/topic:plugin-directory
[3] http://docs.openstack.org/releasenotes/neutron-lib/unreleased.html#id3

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20161116/e220dfee/attachment.html>

More information about the OpenStack-dev mailing list