I have a project that includes a requirement line this:
-e git://git.openstack.org/openstack/neutron.git#egg=neutron
Every time update.py runs against the file, it adds an extra newline
after this. For example, if I run update.py a few times, I'll have a
few new lines in the file. This patch prevents the extra newlines
from getting added.
Change-Id: I92d02a45c437025b16df067d7b58a3727d42c0e0
Signed-off-by: Russell Bryant <rbryant@redhat.com>
Pin yaql to 0.2.6. 0.3.0 should be excluded and is already excluded
in global-requirements.txt, but commit b0eddd76 landed after
upper-constraints.txt was introduced.
Current version of yaql (0.3.0) blocks Murano dsvm jobs.
Change-Id: Icc0d2c2c796d21cd93b2211f23dbb75c68e307a6
constraints files, unlike global_requirements, need to be able to
contain urls (specifically file:/// paths) so that we can constrain
libraries to be run from their git trees, rather than having them flap
all over the place as different servers specify different bounds. The
first edit-constraints implementation failed to parse such lines,
throwing errors instead.
This patch makes the support for urls optional, preventing changing
the semantics of requirements update.py logic.
Change-Id: I33bd2d9dff9cb7dc1a50177db7286b7317966784
Depends-On: I0f07858e96ea3baf46f8a453e253b9ed29c7f7e2
yaql 0.3.0 was developed as proof-of-concept, and later was
completely redesigned, it's not recommended for production usage.
Murano & Mistral will not be able to consume 0.3.0 as well, that's
why we should restrict installation of 0.3.0.
Change-Id: I25540b1be8a15e8ab83a9646693901e2af5e33cf
This will provide space to store the result of parsing requirements
like -e file:///opt/stack/new/oslo.THING, which we need to do for
edit-constraint to work in devstack when more than one library is
being installed from git. This is a separate patch to make reviewing
the actual new functionality easier - it is entirely mechanical,
adding the field and dealing with test fallout.
Change-Id: Ied4e92717b0dab871dac42ae639d1f2a6c236414
Ceilometer, Cinder and Nova using redis backend
require tooz>=0.16.0 to work properly.
blueprint tooz-for-service-groups
Change-Id: I0458c7e58eeaa9e2460e78e23e321e394f2bc633
A key resource leak was fixed in 1.3.1 and we can't switch to using
until we can depend on 1.3.1 being the version present.
Change-Id: I8c01506894ec0a92b53bc0e4ad14767f2dd6a6b3
2.1 breaks Nova as well, earlier we excludeded just 2.0, we
should exclude 2.1 as well
Closes-Bug: #1469883
Change-Id: I94151624dad266532b3db7d29da1be21f46a6190
Looks like the release today did not go well and is breaking
tests in cinder and nova. So let's exclude this version from g-r.
Change-Id: Id62fedd6ee629cb466ff2829cc7af8da185a5c3c
This version introduced an important retry-on-conflict feature,
which can be used instead of ad-hoc implementations e.g. in Nova
and ironic-inspector.
Change-Id: I4b37271b23f63ea4380fcc9e229763e1935b8a06
This allows shell editing of a constraints file, which we need to do
in devstack when installing a constrained library from git.
Change-Id: Ibdbfc786b5d2f56d2e41d329c8766bef7b2e6854
Allow projects to kick the tires of oslo.cache and oslo.reports.
oslo.cache was extracted from keystone and is based on dogpile
interfaces. oslo.reports was extractred from oslo-incubator and
is widely used (copied). We would like projects to try to adopt
these libraries and provide valuable feedback on the API.
Change-Id: I8184ade8989349ffca9a71c4ae1b56ca12fecbec
This library will be used by ironic, taskflow, oslo.messaging
and others in the near-future so adding it here to enable that
integration to commence.
Change-Id: Id2caa2a77b139d1a94349882f77da60d425dead5
oslo.db 1.12 now uses the PyMySQL driver for MySQL by default, instead
of MySQL-python. This change is required to replace MySQL-python driver
with PyMySQL in applications. Otherwise, migration tests are skipped.
The following changes require oslo.db 1.12:
* I66b7d6053643e82d9c11af568190d82ffe7f385e (glance)
* I590c26523f4dc8d14c45e61bb89555486629b64d (nova)
Change-Id: Ia9eeaf78ff4dd5831213bbcb8a9f364d0e49bc5e
We shouldn't be able to bump global requirement versions if that
would be incompatible with the current test set of versions. To assess
'works' we need to run them in tests which means that we need to
update upper-constraints.txt at the same time. We don't test all
versions however, so just checking that the constraints version is
compatible with the updated global requirements is sufficient.
This adds a dependency on the pypa packaging library. The library is
maintained by the authors of setuptools and pip, is Apache V2, in good
condition and Python 3 ready. Its a test-only dependency so I don't
think the distro packaging status matters. This is *the* reference
library for packaging facilities on Python.
Change-Id: I032dd9a384453dcfa4911ea905c8f89b0c974211
swift was added in 9b6a2b9050290bda548872cf444da6021f2aaeef as the
result of a mass script run over everything: we don't have any other
servers in global-requirements, and as swift doesn't offer a library
interface (and isn't meant to be on PyPI) it doesn't make sense to
have it.
Change-Id: Iba7dd6a705ed5bdc8836bcfd0f511f6bf0e00ed7
The release 0.6.0 of tempest-lib contains backwards incompatible
change, and Tempest gate jobs continuously failed.
The Tempest gate problem has been solved with some workaround, but
tempest-lib is a library. So we need to avoid the same problem on
the other project gates.
The release 0.6.1 has been released now for avoiding backwards
incompatible change, this patch changes tempest-lib version for
using the latest release.
Change-Id: Ica2d61a6807721c5e715a2130bd25e719acc9b03
Related-Bug: #1468149
Enable futures for 2.6 this until the discussion around oslo.messaging
need for this (and its support for 2.6) and its planned usage of the futurist
library for the liberty release.
Also some of the current oslo libraries (taskflow) still support 2.6
for the short-term (until a few other reviews merge) so we need to enable
its usage there still for enum34.
This is also breaking the futurist, automaton, gate and the taskflow check
gates as those are still on 2.6 (this may change soon).
Soon the following will make that less relevant (but these haven't merged
yet):
- https://review.openstack.org/#/c/193349/
- https://review.openstack.org/#/c/193354/
- https://review.openstack.org/#/c/194860/
Change-Id: I9256563a6c2cc455043f0d61cd27b033d37302ef
Nova needs the new release of oslo.concurrency in order to be able
to cleanup security bug 1387543.
Change-Id: I08693891b2b4c1d4c166e41b38adc6776e25d8e5
Related-Bug: #1387543
