This replaces the requirements.stub dependency approach for
heat_integrationtests with a single dependency on tempest in
test-requirements.txt.
tempest provides all the required dependencies for the current
heat_integrationtests, and this helps the transition of being able to
run tests both with the current runner and as a tempest plugin.
blueprint tempest-plugin-support
Change-Id: I6fc5886feec5de71826f640cd29990114bd7781c
This removes the in tree copy of os-api-ref and migrates to the
upstream released version. It will fix the issues with the style
because the static files weren't in the right place in tree.
Change-Id: Id3a71841f5b9a9ea7bb5803afd967ab4feadfe10
We have broken gate, because we have no limitation to fixtures,
and the new version is incompatible to us.
We need to add fixtures into test-requirements to make
sure that we always up to date with global requirements.
Closes-Bug: #1567731
Change-Id: Ib0cac0c217db195ce3723cee3f09d26e6be9f0ea
The problem of integration tests was that they use their own
requirements.txt that is unable to auto-sync with global requirements.
This patch removes dedicated requirements.txt and replaces it with a
stub file listing names (and possibly versions) of the packages needed.
Then a special script parses this stub file, and for every package
that is present in main project requirements files it pulls the versions
from main project requirements, generating and installing requirements
for the integration tests on the fly.
This will help keeping requirements for the integration tests always in
sync with main project requirements.
Change-Id: Ie79338cc10cc101fbf15b51c7923e3a7b8e4fbb4
Closes-Bug: #1490866
oslo.messaging has kombu in its own requirements, so kombu
is not needed in requirements.txt.
Instead it was moved to test-requirements.txt file because
it is explicitly imported for functionnal tests.
Change-Id: I952263f1d2c61a3b700824914da499b1ece91b78
If we use oslo.db fixtures, we'll need these 2 packages or
the next version of oslo.db release will break us.
Change-Id: I71f001c8b75ad52e68ccab8f07cd8946772fd03b
Closes-Bug: #1503501
qpid-python is only needed if the qpid backend is actually used.
when it is part of requirements.txt, loading of heat-engine
(which is done via stevedore) fails as it forcefully requires
qpid-python then. However heat seems to work just fine without it.
Change-Id: I1c49ec709995da145849d8616fe7207908637fb9
Add a tox environment for bandit so it can be run as a gate job
eventually. As-is, there are no high severity issues detected in heat.
Change-Id: Iab098a1d8bac5c95d67e6867ad5249987c3a786e
As discussed in the Liberty Design Summit "Moving apps to Python 3"
cross-project workshop, the way forward in the near future is to
switch to the pure-python PyMySQL library as a default.
https://etherpad.openstack.org/p/liberty-cross-project-python3
Also set the OS_TEST_DBAPI_ADMIN_CONNECTION override variable so
that oslo.db opportunistic detection will know to use PyMySQL until
I12b32dc097a121bd43991bc38dd4d289b65e86c1 makes it the default
behavior.
Change-Id: I17e052215ce6e1604cdda848ccc20862452ccbc7
Co-Authored-By: Victor Sergeyev <vsergeyev@mirantis.com>