[openstack-dev] [neutron] reusable code moving to neutron-lib

Boden Russell bodenvmw at gmail.com
Mon Oct 30 17:04:31 UTC 2017

Just a quick update on the neutron-lib workstream.

Although there hasn't been many "neutron-lib impact" emails lately, the
effort is still active. The reason for decreased email volume is that
rather than just updating stadium consumers during consumption [1], all
(stadium/non-stadium) consumers who use neutron/neutron-lib stable
branches are updated (for ~free).

To summarize what this means:
- If your project uses neutron/neutron-lib stable branches, you should
see consumption patches as we consume [1] in neutron. Just help the
review along please.
- If your project "pins" older versions of neutron/neutron-lib, your
project will need to address the consumption as you move the "pin" up.
- To stay up to date on the latest neutron-lib consumption patches,
please consider attending the weekly neutron meeting and/or checking the
open patches tagged with NeutronLibImpact [2].

Finally; a heads up that the neutron.plugins.ml2.driver_api module is in
lib and will be removed in neutron as part of consumption [3]. For those
using stable branches, a consumption patch should already be queued up
in your gate [4].


[3] https://review.openstack.org/#/c/488173/
[4] https://review.openstack.org/#/q/topic:use-lib-ml2-driverapi

More information about the OpenStack-dev mailing list