[openstack-dev] [all] ALL dependencies pinned in devstack-gate now

Robert Collins robertc at robertcollins.net
Fri Jul 3 09:17:22 UTC 2015

On 3 July 2015 at 21:01, Thierry Carrez <thierry at openstack.org> wrote:
> Robert Collins wrote:
>> I want to give an update on
>> http://specs.openstack.org/openstack/openstack-specs/specs/requirements-management.html
>> - we've just passed a critical milestone there, and this affects how
>> everyone updates requirements.
>> As of a few minutes ago devstack-gate landed the change to set
>> USE_CONSTRAINTS=True. What this means is that the file
>> http://git.openstack.org/cgit/openstack/requirements/tree/upper-constraints.txt
>> is now used to determine the version of every dependency that is present in it.
> Great to see progress here !
>> [...]
>> Now, the things you have to remember as developers:
>> * If you are adding a new requirement you should also add it to
>> upper-constraints.txt with an exact pin.
>> * If you are raising a minimum version of a requirement, you need to
>> also raise it in upper-constraints.txt.
> Three questions:
> - Do you plan to update openstack/requirements README.rst to explain
> upper-constraints.txt, and how it should be modified in parallel to
> global-requirements.txt from now on ?

Naturally. It already touches on upper-constraints.txt but a full
manual is yet to be written.

> - What should we do with existing requirements reviews ? Reject them if
> they don't come with associated upper-constraints changes ? Check if the
> upper-constraints is compatible ? Recheck them so that a magic test is
> run on them ?

A recheck is sufficient, if its incompatible the unittests will fail

> - Does that (or should that) also affect stable/kilo and stable/juno ?
> (there is no upper-constraints there)

No, and since the disruption of a new pbr and associated minimum
versions throughout stable would be huge, I've no plans to backport
it. If folk wanted to (e.g. if stable suffers from lots of firedrills
even with the caps we added last time) I can throw up some patches and
we can see about it: but its a big effort requiring point releases of
/everything/ (because of the pbr version issue).


Robert Collins <rbtcollins at hp.com>
Distinguished Technologist
HP Converged Cloud

More information about the OpenStack-dev mailing list