From 9702f0d4822555050fe5d266ff34932649eb6317 Mon Sep 17 00:00:00 2001 From: Luigi Toscano Date: Tue, 22 Jan 2019 17:06:23 +0100 Subject: [PATCH] Make sahara (now core only) usable as requirement Starting from Stein, sahara.git contains only the core (services and base classes) of Sahara. The code of plugin was moved into its own repository. Each plugin depends on Sahara core, so in order to use it as dependency it must be added as requirement somehow. No additional splits are planned right now, which means no sahara-lib, which means adding sahara to blacklist.txt * Is the library actively maintained? Yes * Is the library good code? Yes, it is has been part of OpenStack for few years * Is the library python 3 compatible? Yes * Is the library license compatible? Yes,Apache 2 * Is the library already packaged in the distros we target (Ubuntu latest / Fedora latest)? It will be as part of the sahara release * 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, Sahara * If the library release is managed by the Openstack release process does it use the cycle-with-intermediary release type? Right now it uses cycle-with-rc, which still allows for intermediate releases Change-Id: Ia8f2ccfb01492c109fe7d2810f6b441d644c2572 --- blacklist.txt | 3 +++ 1 file changed, 3 insertions(+) diff --git a/blacklist.txt b/blacklist.txt index 38ebc38a5a..659c17b42d 100644 --- a/blacklist.txt +++ b/blacklist.txt @@ -30,3 +30,6 @@ neutron-fwaas neutron-lbaas neutron-vpnaas vmware-nsxlib + +# Sahara uses cycle-with-rc, but it promises a stable plugin interface +sahara