This enforces consistent spacing in global-requirements.txt
and sorts the specifiers to be always in a specific order
(namely minimum bound first, then exceptions, then upper bound).
Add test coverage for this normalisation.
Change-Id: If41732bfe4476e422bc6b9f9f896eb978db8be84
This release fixes a problem with 410 redirect rule parsing that allows
it to be used in the nova tests.
Change-Id: I36003d3525dcc9fef8e5f008ecabb2b2ac78088e
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
RSD client has released the first version of its OpenStackClient
plugin. Since we would like to add this plugin into OpenStackClient
doc, we need rsdclient to be part of this list so that other projects
could add it into the requirements.txt.
Questions for new requirement:
1. Is the library actively maintained?
Yes, python-rsdclient released the initial version in this month and
will continue to support further RSD version in the future.
https://github.com/openstack/python-rsdclient
2. Is the library good code?
This library followed the OpenStack convention to add all necessary
unit test cases, and the OpenStackClient plugin provided by this
project has passed related OpenStackClient tests.
3. Is the library python 3 compatible?
Yes, it is compatible with python 3, and passed all python 3 test
cases.
4. Is the library license compatible?
Yes, it released under Apache 2.0 license.
5. Is the library already packaged in the distros we target (Ubuntu
latest / Fedora latest)?
Current it has not been packaged in any distros, because it just
released the initial version 0.1.0.
6.Is the function of this library already covered by other libraries
in global-requirements.txt?
No, this library provides the specific RSD OSC plugin, which it
reason why this library is created.
7. Is the library required for OpenStack project or related dev or
infrastructure setup? (Answer to this should be Yes, of course) Which?
Yes, when add the RSD plugin into OpenStackClient plugin list, it
requires it has been add global requirements at first, then OSC will
install it to automatically generate usage document.
https://review.openstack.org/#/c/511683/
8. If the library release is managed by the Openstack release process
does it use the cycle-with-intermediary release type?
This project is not released by the OpenStack release project, because
it is not official OpenStack project, but only provides specific RSD
plugin to allow user to invoke RSD API through OpenStackClient.
9. Do I need to update anything else?
No, the initial version also has been added into upper-constraints.txt.
Change-Id: I156cdfbd0afaf9f7e5f41749545e2b8bff663b96
It is similar to flake8 a generic static code linter
and not necessary for building a binary distribution
of OpenStack, so enforcing a g-r consistent version
seems to be slightly over the top
Change-Id: I3907050a3aaab9d32f9b71c14c47212ba793b58d
In order to be able to test the job that proposes upper constraints
updates, we need to have the test deliverable in the requirements
list.
Change-Id: I663a9cde0ab777611cc003fffdc28ff54b46ac05
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Version 1.28.0 of oslo.versionedobjects add support for the
TimestampedObject mixin. The placement service within nova
wants to use this functionality to avail itself of
updated_at and created_at fields in a consistent fashion.
upper-constraints already has ovo at 1.28.0.
Change-Id: Ia94ce24627072eb91df2370b40e1680dd8eacde9
Changes in oslo.cache 1.26.0 are required by os-traits to implement
a memoize function using 'kwarg_function_key_generator' as key
generator.
Change-Id: If4f244ae33ca14f94aaf9a46335c1e0514ea45ea
Release 0.2.0 includes a new feature to support redirecting with a 4xx
response code that is needed to test nova's in-tree .htaccess file.
Change-Id: Ia24cdc5783e2b7e115f8bb3a9560c3991146b548
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
pyroute2 is a pure Python netlink library. The only operating system
supported is Linux (POSIX), as documented in [1]. Installation of
this library should be done only in a Linux OS.
[1] https://pypi.python.org/pypi/pyroute2
Change-Id: I6c39b47ff6abddf57c9ca58d2732d7cc44de1dfb
sadisplay is a python package for creating entity relationship diagrams
from SQLAlchemy models. The Octavia project would like to use this to
generate a database diagram for the developer reference documentation [1].
[1] https://review.openstack.org/#/c/509319/
Is the library actively maintained?
Yes - https://pypi.org/project/sadisplay/#history
Is the library good code?
Yes, it is pretty straight forward code
Is the library python 3 compatible?
Yes
Is the library license compatible?
Yes - BSD
Is the library already packaged in the distros we target?
No
Is the function of this library already covered by other libraries?
Not that I am aware of
Is the library required for OpenStack project?
Yes, Octavia would like to use it in: https://review.openstack.org/509319
If the library release is managed by the Openstack release process?
N/A
Change-Id: Ie05f42f9357dfd662844ad3c2850c7eacf23e5a4
Cliff 2.9.0 has an issue [1] with some packages such
as ptyprocess.
Trove pulls in ptyprocess through its pexpect requirement,
and as such Trove's gates are blocked by cliff 2.9.0.
[1] https://bugs.launchpad.net/python-cliff/+bug/1719465
Change-Id: I2867563b9bf1fb37c08cc732da54140fdc3e5cb6
It adds connection.stop() and I46681c7649d604d9a3fc5ad2c4c91167fe4873ee
needs that. Other projects can also use it to more cleanly shut down
connections to ovsdb-server.
Change-Id: I3ab364cc217d4887deb438e328852c60cebbadbf
networking-ovn metadata agent requires ovsdbapp.backend.ovs_idl.event
which is present from ovsdbapp 0.5.0 on. This patch bumps the minimum
version to this.
Change-Id: I701e0857c576957b704a5f336c63298a9702dca2
Signed-off-by: Daniel Alvarez <dalvarez@redhat.com>
oslo.db will NOT throw the deprecated DbMigrationError since 4.27.0
Consumers should use DBMigrationError instead.
Reference: Ibb2f105c58252adb7dfe4f1a7d6643410ac031b3
Change-Id: I0ebd69c3d778acb5bec9e136627e345e7fcf2bd3
The upper constrains for neutron-lib have already been bumped for 1.10.0
in I60e815157a84bb50140db526ba31dc2000d9c2ee, but we'd like to see the
requirement change propagated into all consumers so that we can begin
using the lastest changes in neutron-lib.
This patch bumps neutron-lib to 1.9.0 so consuming requirements.txt
will be updated allowing us to use the latest release in neutron and
other networking projects. For a list of features see the "highlights"
in Id21fe608c0261f52154dfc15fc0de0873d9c24d7.
Change-Id: Ibe7a283101e8558331e89ead749e5653b6372876
networkx 2.0 has released but is not backwards compatible with 1.0.
Avoid it for now.
Partial-Bug: #1718576
Change-Id: If394af569790b38106fd4cb18266ef0300703e87
Commit 8980bf7da55dd084ad84c84534fe937f0d43b9c0 in Castellan deprecated
config option key_manager.api_class, switching to use key_manager.backend.
In order for consumers to switch to using backend, we need to ensure the
version of castellan used is at least 0.13.0 to have this option present.
There were some known issues with 0.13.0, so jumping up to the 0.14.0
release.
This is causing at least Cinder docs builds to fail due to treating
warnings as errors and getting deprecation warnings during the build.
Related-bug: #1718468
Change-Id: I112f7a4654a65c3291526b408838d7b1c175b069
In 0.3.x, it contains several bug fixes and also supports some new
features: e.g. xapi pool, vdi streaming.
This is to switch os-xenapi to the latest os-xenapi 0.3.1.
Change-Id: I80007bb897a1f7eda47ebda82e08fe270f97ff40
If available, we use as the lower bound the version that
was in upper-constraints in Kilo, or whichever OpenStack
version later than that where it was first added.
Change-Id: I458feff015e1fc16af7af57710a3077ae8c5e28e
In marathon 0.9.1, python3 support is broken,
it is fixed in master. It breaks any python3 job,
if 0.9.1 is used.
Issue:
https://github.com/thefactory/marathon-python/issues/217
Change-Id: If802ae734d0a9eba48dcfcfa370f3a2bca0ece17
This commit bumps the minimum requirement of os-testr to 1.0.0. This new
release changes the test runner used internally to stestr. Since this is
a major internal change it'll be better to switch it early in the cycle
to shake loose any potential bugs.
Change-Id: Iabe4217c6aa52cb4d3a715756e0b8c46a6d553d0
oslo.privsep gained many new constants with I1e6f7bff66495cdb83428a6c3b62804e5d20fc3b
which is included in the 1.23.0 release. In [1] those values are simple
open coded. Raising the minimum allows nova to use the new constants.
[1]: https://review.openstack.org/#/c/459166/33/nova/privsep/__init__.py@30
Change-Id: Icaeb2800a009b996c8eefe91916eeefcd5bca6a2
pypowervm 1.1.7 contains a number of bugfixes and important features
needed in nova for PowerVM, including support for I/O slot usage
information (needed by
https://blueprints.launchpad.net/nova-powervm/+spec/pci-passthrough).
Change-Id: Icb7a5c0804e6722170b973d8522987b413dd5f3f
Once the gate issue is sorted in openstack-ansible_os_tempest
we should undo this patch, as requirements and upper-constraints are actually correct.
This reverts commit afd39d8ac3464e280c964cfc4336298c2729ca8d.
Change-Id: I3bd3a5485f1b54adef4a4be7d3edc05a43af4aad
Shade 1.23.0 has a bug that causes ansible os_image module
to fail. Reverting to 1.22.2 would solve our issue.
This reverts the bump and blacklists the impacted version.
Change-Id: I1387b538b96e428dd3dc6d2e3f9e9fbb6fd2e9cf
Closes-Bug: #1715603
Based on testing against the g-r set of cross checks, which includes
dsvm, grenade, unit and functional tests of glance, cinder, nova, neutron
and swift, these seem to be the lower bounds that are actually coinstallable
and passing all tests.
Change-Id: I4a193295081593a9df6c34b5c263b1b8becadbda
Most of them were neglected and pointed to versions released
a year ago and more, which are typically not installable anymore
(they used to have a pbr<2.0 requirement which is incompatible
with the pbr>=2.0 requirement we enforce globally).
So for all of the openstack affine projects, update to a release
that is less than 4 months old (in some cases even newer versions
were required upon trial and error).
Change-Id: I69472a6a99b857e9e5dad9052eda7172ae2c9525
whereto is developed on OpenStack infrastructure. I am in the process
of having the docs team adopt it for maintenance.
Is the library actively maintained? - Yes. This is an OpenStack
community product.
Is the library good code? - Only the best.
Is the library python 3 compatible? - Yes. It has the standard python
3 unit test jobs in its gate.
Is the library license compatible? - Yes, Apache 2.
Is the library already packaged in the distros? - No, but it's a doc
build tool so it may not need to be.
Is the function of this library already covered by other libraries? -
I was unable to find any similar tool that could be downloaded and run
in CI anywhere at all, so no.
Is the library required for OpenStack project or related dev or
infrastructure setup? - It is a tool for testing redirect rules and
will be an optional component in doc CI jobs. The documentation team
is already using it (the openstack-manuals repo does not follow the
global requirements process).
If the library release is managed by the Openstack release process
does it use the cycle-with-intermediary release type? - It will likely
continue to use the independent release model after being formally
adopted, but that is not decided.
Change-Id: I67e9453367cfd26b862a18a87a0b135a28ca756c
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
