[openstack-dev] [requirements][neutron] Depending on pypi versions

Gary Kotton gkotton at vmware.com
Mon Mar 19 13:01:32 UTC 2018

The issue is that since the change below - https://review.openstack.org/553045 - we are not picking up the latest neutron master code.

From: Thomas Morin <thomas.morin at orange.com>
Organization: Orange S.A.
Reply-To: OpenStack List <openstack-dev at lists.openstack.org>
Date: Monday, March 19, 2018 at 1:46 PM
To: OpenStack List <openstack-dev at lists.openstack.org>
Subject: Re: [openstack-dev] [requirements][neutron] Depending on pypi versions

Hi Gary,


> Note that thanks to the tox-siblings feature, we really continue to
> install neutron and horizon from git - and not use the versions in
> the global-requirements constraints file,

I think it is worth adding a comment in (test-)requirements.txt that the OpenStack CI is overriding the version and uses git.


Gary Kotton, 2018-03-19 11:25:
The change https://github.com/openstack/requirements/commit/35653e8c5044bff1059ddddf50a82b6065176eea has created some issues with decomposed neutron plugins. Let me try and give an example to explain.
Say for example a patch landed in neutron master that exposed feature X. Now if a decomposed plugin wants to consume this it will fail as the decomposed plugin will pull in the latest tag.
Does this mean for each new feature that we wish to consume we will need to update neutron tags?
Please advise.
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at lists.openstack.org<mailto:OpenStack-dev-request at lists.openstack.org>?subject:unsubscribe
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20180319/198bc7fb/attachment.html>

More information about the OpenStack-dev mailing list