From 52fb459e52d158a9eca3523aeba171e254ad65d4 Mon Sep 17 00:00:00 2001 From: Peter Penchev Date: Sat, 7 Sep 2019 11:35:11 +0300 Subject: [PATCH] Add two StorPool libraries for the Cinder StorPool driver. * Is the library actively maintained? Yes, both libraries are maintained by StorPool. The "storpool" library is actually part of the StorPool distributed storage software, it is installed in each deployment since the StorPool tools use it. The "storpool.spopenstack" library is installed as part of each deployment of StorPool on an OpenStack controller or hypervisor. * Is the library good code? We would certainly like to think so. Both libraries are open-source and we would welcome reviews and comments. * Is the library python 3 compatible? Yes, the StorPool third-party CI at https://spfactory.storpool.com/ runs the Cinder-related Tempest tests using Python 3.7 on Ubuntu 16.04 (Xenial). * Is the library license compatible? Yes, both libraries are under an Apache 2.0 license. * Is the library already packaged in the distros we target (Ubuntu latest / Fedora latest)? Not yet, but we have WIP packages that we already install at some of our customers' locations. We intend to add them to Debian and, hence, Ubuntu, and we will offer our full assistance to anyone who wants to officially package them for Fedora. * Is the function of this library already covered by other libraries in global-requirements.txt? No; these libraries are closely related to Python language bindings for the StorPool distributed storage system API, there is no other package that offers similar functionality. * Is the library required for OpenStack project or related dev or infrastructure setup? (Answer to this should be Yes, of course) Which? The StorPool volume driver within Cinder uses both the storpool and storpool.spopenstack libraries. The goal of adding them to global-requirements is to subsequently add them to Cinder's setup.cfg file in the [extras] section, so people who want to install the Cinder Python library and have the StorPool driver work will have them pulled in as needed. See also https://review.opendev.org/680530 * If the library release is managed by the Openstack release process does it use the cycle-with-intermediary release type? N/A Change-Id: I947c5a0087225668523e4aa249b1b11ef9b850e9 --- global-requirements.txt | 2 ++ upper-constraints.txt | 3 +++ 2 files changed, 5 insertions(+) diff --git a/global-requirements.txt b/global-requirements.txt index 63af5f2c84..1b9c0706a8 100644 --- a/global-requirements.txt +++ b/global-requirements.txt @@ -227,6 +227,8 @@ PyMySQL # MIT License python-etcd # MIT License pywbem # LGPLv2.1+ salt # Apache-2.0 +storpool # Apache-2.0 +storpool.spopenstack # Apache-2.0 tap-as-a-service # Apache-2.0 etcd3 # Apache-2.0 etcd3gw!=0.2.2,!=0.2.3 # Apache-2.0 diff --git a/upper-constraints.txt b/upper-constraints.txt index 7dc87ca168..5a4d8f69bc 100644 --- a/upper-constraints.txt +++ b/upper-constraints.txt @@ -12,6 +12,7 @@ python-saharaclient===2.2.1 python-hnvclient===0.1.0 Routes===2.4.1 rtslib-fb===2.1.69 +confget===2.2.1 XStatic-Angular-Bootstrap===2.2.0.0 paunch===5.1.0 WebOb===1.8.5 @@ -218,6 +219,7 @@ prometheus-client===0.7.1 oslosphinx===4.18.0 mox3===0.28.0 gunicorn===19.9.0 +storpool===5.1.0 textfsm===1.1.0 python-3parclient===4.2.10 unittest2===1.1.0 @@ -628,6 +630,7 @@ python-blazarclient===2.2.0 alembic===1.1.0 glance-store===1.0.0 sphinxcontrib-programoutput===0.14 +storpool.spopenstack===2.2.1 sphinx-testing===1.0.1 dnspython===1.15.0;python_version=='3.4' dnspython===1.15.0;python_version=='3.5'