This introduces tooz.hashring, lifted from nova and ironic. We need to
bump the minimum to rip the copy-pasta out of those projects.
Change-Id: Ic1f8b89b819ace8df9b15c61eaf9bf136ad3166b
It is needed to fix a bug in retrieving pre-existing
config-drive partitions.
Change-Id: Ia1b72173dabb640e59b4825283bf810da2070963
Depends-On: I33ff46d771ce3f799ebbe88fdefef0f34be71a61
The OpenStack heat-translator project needs to use newly introduced APIs
in the tosca-parser 0.7.0
Change-Id: Ie5b7c03ecda874997f17733354c127b0587c59a5
The OpenStackClient team created a meta-package, openstackclient,
which includes all known OSC plugins, to compliment the usual
python-openstackclient library. It'll need regular proposal bot
updates.
Change-Id: Id3551d696ba3b35dc688291ae063dfe2ca94880e
We need the container_update API introduced in 1.8.0,
but 1.8.0 was blacklisted, so we require 1.8.1 or newer.
Change-Id: I588edc2383c6f71748232b5560607526f1fef2d4
This library provides the equivalent functionality of weakrefmethod
in python3. This will be used by Neutron. This patch doesn't update
upper-constraints.txt because we implicitly depend on this library
so it's already present.
- Is the library actively maintained?
Not really, but it's a one function library that accomplishes its goal
so there isn't much to maintain.
- Is the library good code?
Yes, it's pretty easy to follow for the complex thing it achieves
(weak references to bound methods).
- Is the library python 3 compatible?
No, but the purpose of this library is to provide a python3 function
so we can use it in python2.
- Is the library license compatible?
Yes. It's PSF.
- Is the library already packaged in the distros we target (Ubuntu
latest / Fedora latest)?
I assume so, we already depend on it via the notifier library.
- Is the function of this library already covered by other libraries
in ``global-requirements.txt``?
No
- Is the library required for OpenStack project or related dev or
infrastructure setup? (Answer to this should be Yes, of course)
Which?
Yes, Neutron for a callback handling system. See
I7576851a44abd14cbc337a3d3e28690c7316ec81
Change-Id: I8e6173342bd2ab4f9f31b3aaa1452e838770fa06
zhmcclient is a python binding for the IBM z Systems
ReST API in DPM (Dynamic Parition Manager) mode. zhmcclient is used
by nova-dpm [1] and networking-dpm [2].
Nova-dpm contains the dpm virt driver for nova compute. It uses
zhmcclient to CRUDL instances.
Networking-dpm contains a mechanism driver for the neutron server
and the dpm neutron l2 agent. It requires zhmcclient for networking
related configuration.
Neutron-l2 agent and nova-compute both run on the compute node. The
compute node can be any system that has access to the HMC ReST
API. This can be another z Systems, but also an x86 system.
The controller node (with the dpm neutron mechanism driver) does not
need access to zhmcclient.
- Is the library already packaged in the distros we target (Ubuntu
latest / Fedora latest)?
No!
- Is the library actively maintained?
yes!
Commits history: https://github.com/zhmcclient/python-zhmcclient/commits/master
Release history: https://pypi.org/project/zhmcclient/#history
# of releases in 2016: 9
- Is the library good code?
Travis testing (unittest) for various python version in place:
https://travis-ci.org/zhmcclient/python-zhmcclient
Test Coverage: ~86% (https://coveralls.io/github/zhmcclient/python-zhmcclient)
- Is the library python 3 compatible?
Yes! Python 3.4 and 3.5 test jobs in place
- Is the library license compatible?
yes! Apache 2.0 license
- Is the function of this library already covered by other libraries
in ``global-requirements.txt``?
No!
- Is the library required for OpenStack project or related dev or
infrastructure setup?
yes!
* networking-dpm [1]
* nova-dpm [2]
[1] https://launchpad.net/networking-dpm
[2] https://launchpad.net/nova-dpm
Change-Id: Ied0654e01ef8a3c069dec7645e903ad4b421502a
There is a bug within ansible and/or jinja2 that causes an exception
when a string contains curly braces. A bug has already been opened
with the Ansible team to review the bug.
This patch pins the jinja2 release at a version less than 2.9. The
issue first appeared in the 2.9 release and is still present in
2.9.4 (latest available).
Jinja2 bug: pallets/jinja#654
Ansible bug: ansible/ansible#20098
Related-Bug: 1655397
Change-Id: I82561d3d738147683499697883d9d03ceb897f3d
