Re: [openstack-dev] [neutron] neutron-lib impact: neutron.plugins.common.constants are now in neutron-lib
On 5/3/17 8:55 AM, Eric Fried wrote: > Can you please point to the change(s) that move the constants? Or > provide some other way to figure out which are affected? > This Hound search [1] provides an overall picture and can be honed to specific projects as needed. The search will identify all modules that import the constants, but the respective source will need to be inspected to determine which constants are applicable to neutron-lib. Also, feel free to reach out to me ('boden') on #openstack-neutron if there's questions/comments/etc.. [1] http://codesearch.openstack.org/?q=from%20neutron%5C.plugins%5C.common%20import%20constants __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [neutron] neutron-lib impact: neutron.plugins.common.constants are now in neutron-lib
Boden- Can you please point to the change(s) that move the constants? Or provide some other way to figure out which are affected? Thanks, Eric (efried) On 05/03/2017 09:30 AM, Boden Russell wrote: > If your project uses neutron.plugins.common.constants please read on. If > not, it's probably safe to discard this message. > > A number of the constants from neutron.plugins.common.constants have > moved into neutron-lib: > - The service type constants are in neutron_lib.plugins.constants > - Many of the others are in neutron_lib.constants > - A few have not yet been rehomed into neutron-lib > > Suggested actions: > - If you work on a stadium project, you should already be covered [1]. > - Otherwise, please move your project's imports to use the constants in > neutron-lib rather than neutron. See the work in [1] for reference. > > Once we see sub-projects moved off these constants, we'll begin removing > them from neutron.plugins.common.constants (likely as a set of patches). > We can discuss this topic in our weekly neutron meeting. > > Thanks > > > [1] > https://review.openstack.org/#/q/message:%22use+neutron-lib+constants+rather%22 > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [neutron] neutron-lib impact: neutron.plugins.common.constants are now in neutron-lib
If your project uses neutron.plugins.common.constants please read on. If not, it's probably safe to discard this message. A number of the constants from neutron.plugins.common.constants have moved into neutron-lib: - The service type constants are in neutron_lib.plugins.constants - Many of the others are in neutron_lib.constants - A few have not yet been rehomed into neutron-lib Suggested actions: - If you work on a stadium project, you should already be covered [1]. - Otherwise, please move your project's imports to use the constants in neutron-lib rather than neutron. See the work in [1] for reference. Once we see sub-projects moved off these constants, we'll begin removing them from neutron.plugins.common.constants (likely as a set of patches). We can discuss this topic in our weekly neutron meeting. Thanks [1] https://review.openstack.org/#/q/message:%22use+neutron-lib+constants+rather%22 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev