[openstack-dev] [neutron] Proper usage of neutron extensions/modules

Boden Russell bodenvmw at gmail.com
Thu Feb 15 16:09:56 UTC 2018


If your networking project is using neutron/neutron-lib, please read on.

SUMMARY:
If you're using neutron or neutron-lib code (for example extensions),
please ensure you import/use the respective attributes of those modules
rather than duplicate such values (str constants and such).


DETAILS:
To fully consume neutron-lib changes; the respective code that was
rehomed into lib is removed from neutron once all consumers using stable
branches are updated to use lib (instead of neutron). In order to find
such consumers we generally search [1] for who imports the respective
modules of interest. This allows us to update the consumers and ensure
they don't break once we remove the code from neutron.

The implication is that if consumers are using (depending on) the
neutron code, but never import it, they are missed in this process and
can end up with breakage when we remove the code from neutron.

A recent example of such includes [2] mentioned on [3].
An example of what's being asked for can be found in [4].


ACTION:
If neutron consumers could please inspect their code to ensure they are
declaring their intent to use neutron with 'imports' and also use
neutron module attributes were applicable, we can minimize the number of
breakages that occur in this process.


Feel free to reach out to me (boden) on openstack-neutron with any
questions/comments.

Thank you!


[1] http://codesearch.openstack.org/
[2] https://review.openstack.org/#/c/544179/
[3]
http://lists.openstack.org/pipermail/openstack-dev/2018-February/127385.html
[4] https://bugs.launchpad.net/kuryr-libnetwork/+bug/1749594




More information about the OpenStack-dev mailing list