It's somewhat strange to say you can build a package with pbr >= 1.8 but
to install it you need 2.0.0. Synchronise these values.
Change-Id: I47640a0226be2e82f2fbbf866d2c235f5e7ed415
This contains bug fixes for:
- Fix exception when a security group rule is created
- Security enhancements for certificates
Change-Id: Iaec3cf149db3eae6dbc9b8485a104f6cd7ec8558
Closes-bug: #1668975
The 3.20.0 release of oslo.utils includes a new parameter for generating
UUIDs that indicates if dashes should be included in the resulting UUID.
This is needed by python-barbicanclient:
I95a4a8c8e9b4501d4f9796309beb50971f2a7222
Change-Id: I3ce139b04853cd2f58fd10adfca4415537433d42
The 3.10.0 release of oslo.middleware introduced a new method for cors,
set_defaults, which allows the setting of defaults more easily.
At least two projects trying to take advantage of this feature:
Barbican: https://review.openstack.org/#/c/394064/1
Cinder: https://review.openstack.org/#/c/393577/15
Change-Id: I6979a1089bdce84d8f9b0fd9322000a5d45a493a
The requirement hasn't been updated for a long time and other
components are no longer compatible with the older version (mainly, new
workflows were added).
Change-Id: I56864050f1d01c9f9d50a31f1eddabb241d1140e
This is a follow-on to I8bc3f0e84b2812bbf7f8a9f54c870115ebbb052d.
34.3.0 [1] was released a few hours ago (as of this writing) and still
exhibits the same problem. Bump excludes up to this new release.
[1] https://github.com/pypa/setuptools/releases/tag/v34.3.0
Change-Id: I9c57c08a150571c5bb62235d502839394d53a4c1
A recent release of neutron-lib added minor enhancements
that neutron and its sub-projects would like to adopt.
Change-Id: I43202c91b90df019a502922ed2d6b1ee3ddc4c5b
Keystone needs to support better password hashing. The recommended hash
mechanisms is either bcrypt or scrypt. Generally speaking, the sha2 based
hashing is widely considered completely insufficient for off-line
bruteforcing. Currently keystone uses sha512_crypt instead of bcrypt
or scrypt. Keystone will be adding support for both bcrypt and scrypt
and ceasing use of sha512_crypt (except for passwords that were already
hashed with sha512_crypt). Use of passlib.hash.bcrypt requires the
bcrypt libarary, likewise use of passlib.hash.scrypt requires the
scrypt library.
Both bcrypt and scrypt are actively maintained.
These are the standard libraries used by passlib for the given functions.
Both libraries are released and compatible with python 3.
Bcrypt is Apache2 License. Scrypt is BSD-2-clause license.
Bcrypt is packaged for Ubuntu and Fedora. Scrypt is packaged for
Ubuntu but not packaged for Fedora.
Passlib recommends bcrypt instead of the alternative options
especially for python3.
Passlib recommends the scrypt libary as the the built-in backend is
~100x slower than the packaged version.
These will be required for passwords handled in keystone.
Change-Id: Ia549b0b4d7d6c24f9ba3da6daa04e28e441267f5
Having minimum version constraint for falcon>=0.1.6 in g-r and
1.1.0 in upper-constraints is not good.
Basically after release of falcon==0.0.3, the next one
was 1.0.0 and, as falcon documentation says
(http://falcon.readthedocs.io/en/stable/changes/1.0.0.html),
there were some breaking changes. However there are none for
1.1.0 release.
The issue was discovered during monasca-log-api testing with older
falcon and having problems with major falcon's API code differences.
Same issue affects monasca-api.
Ref-1: http://falcon.readthedocs.io/en/stable/changes/1.0.0.html
Change-Id: Ib521441d38fcff942e64a125cde2e0861c4abf4e
This contains bug fixes for:
- Certificate management
- DHCP otions
- this resulted in neutron extra options extension not
working
- add missing tags for firewall sections
- enable switch name to be updated
In addition it also adds support for:
- ability to search resources according to tags
Change-Id: I1221526a8b4bfd23c4e34742997ba18499c193c9
The validation command is not able to handle that and I'm not sure
if it is really worth fixing that.
Change-Id: I8abc66143333522b77ab4ff6b2fef66bc707a36a
we do this manually, once, so that when the bot runs tonight we know
what it's trying to update (sort doesn't hide things).
Change-Id: Iea112dae13be2a0aa3983032524a734e787e99b9
