vmware_nsxlib projects requirements not synced with global by
Openstack Proposal Bot. We need to change this.
Change-Id: If45c5d2995edc76a83af07a7bd2bcd85ef4cdb88
This commit reverts ecdbd1a6e90360f08680f4bba06671fd6203dd47
Newer docker-py also introduces conflicts over requests and
tripleo-common. Reestablish upper cap until this is resolved.
Change-Id: I297785a4407822093d003cab17165941b034b40f
This reverts commit 45c9e922734396bc22a466f316161046e92495a6.
https://github.com/eliben/pycparser/issues/147 is fixed by
removing the bad wheel from pypi.
Change-Id: Id13203ef802cc4e9cc35e8e092a0b08303fcb44d
Related-Bug: #1629830
cliff 2.2.0 suports the formattable columns concept [1].
The feature is required to make JSON or other machine readable format
more useful in OSC or other cliff-based CLI implementation.
Note that we already specify cliff 2.2.0 in upper-constraints.txt.
[1] https://review.openstack.org/#/c/330223/
Change-Id: I39e6af731a2984f7c9b4f61dcccd8f64ffc000aa
os-api-ref is ready for g-r process, so let's do it. It's used
by several server projects to publish the API reference documents.
Also, Dirk asked for this in https://review.openstack.org/#/c/379224 ;)
Change-Id: Ib982a1f46907d9f3dc20d2f938de36e59e16df31
Depends-On: I0f2e4a3e4eb5dbb9379b0bef9e13a8e1ced82db6
sphinx-testing is needed by os-api-ref for testing the theme.
- Is the library actively maintained?
No changes in the last 12 months, but also no open issues.
- Is the library good code?
I believe so, includes tests itself.
- Is the library python 3 compatible?
Yes.
- Is the library license compatible?
Yes, BSD license.
- Is the library already packaged in the distros we target (Ubuntu
latest / Fedora latest)?
Packages found for Ubuntu and openSUSE:
http://packages.ubuntu.com/xenial/python-sphinx-testinghttps://build.opensuse.org/package/show/devel:languages:python/python-sphinx-testing
- Is the function of this library already covered by other libraries
in ``global-requirements.txt``?
Not that I'm aware of.
- Is the library required for OpenStack project or related dev or
infrastructure setup? (Answer to this should be Yes, of course)
Which?
Yes, os-api-ref - which is used to display api-ref of server projects.
Change-Id: I3bb1d25e3b9881b9cf18134f0eac84a8f4aedae6
Implement XFAIL handling for ignoring known problems so that
we can make the job voting until the remaining issues are sorted
out.
Change-Id: Ia2cf2c440a72e6365a9ff08086704dc535bbc072
pylxd had a bug where it consumed so much memory that nova
compute would hang. 2.1.1 contains the fix.
This is the bug: https://github.com/lxc/pylxd/issues/183
Change-Id: I15ac5a40a05e3e9e455e9353159ca5dde23eaf80
Since a new version 0.8.0 of os-testr is released.
It adds following major improvements:
* Allow to specifiy black/white list at the same time
* Make subprocess outputs to text for Python 3
* Add --black-regex/-B option
* Add support for Python versions
http://docs.openstack.org/developer/os-testr/history.html
Change-Id: Idbe484c193b10c3dac1b035744c383c458b344f6
This adds a feature known as inner fixtures[1] which allows
a test harness to add per test request fixtures that can
perform output capture. This is required in Nova's use of
gabbi to be aligned with existing strategies for test logging
and debugging.
[1] http://gabbi.readthedocs.io/en/latest/fixtures.html#inner-fixtures
Change-Id: Ic13dc14f62334aefbcced93872ec564cab157898
in Python 3 The SafeConfigParser class has been renamed
to ConfigParser in Python 3.2 [1]. The alias SafeConfigParser
maybe removed in future versions of Python 3. Use ConfigParser
instead of SafeConfigParser in Python 3.We're switching from
SafeConfigParser to ConfigParser because we're we're not explicitly
using the 'Safe' functionality.So it make the code potentially neater
if SafeConfigParser is even de-aliased in python3.
[1] http://bugs.python.org/issue10627
Change-Id: I932ced300a93040144e89c7f4acc95480b32749d
OVS 2.6.0 was just released. This version includes support for
Python 3. Now that it is officially released, I think we should only
depend on 2.6.0 and up.
Change-Id: I669ec72743a61b0908c461ff0ec3340f8683a6ec
Signed-off-by: Russell Bryant <rbryant@redhat.com>
Nova has been installing an empty policy file in devstack for a while
now because it's not necessary to define rules in policy.json if you are
okay running with the defaults set in code. However oslo.policy did
require that the policy.json file exist, even if empty, until 1.14.0. By
updating the min required version Nova, and other projects, can remove
the useless empty policy file.
Change-Id: I09fa842ffbe75bed269cef6edc9c82d18bfe9297
Due to the rename of the job adding the -ubuntu-xenial suffix,
we have exceeded the path limit and can no longer run inside the
tox environment. shortening to a shorter check name (and renaming
the job) should fix this.
Change-Id: I0927ae81148d15256bd4dfe2a5e48b1819bbe2af
I made a mistake in my initial commit for addining murano-pkg-check
library to the openstack/requirements https://review.openstack.org/#/c/370293/,
I point not existed version of this library in upper-constraints.txt.
It needs to be fixed.
Change-Id: Ic8e0866de0e97f7973b0877c700d4e9894beeb84
