[openstack-dev] [qa] [infra] [placement] tempest plugins virtualenv

Chris Dent cdent+os at anticdent.org
Fri Sep 28 13:39:24 UTC 2018

I'm still trying to figure out how to properly create a "modern" (as
in zuul v3 oriented) integration test for placement using gabbi and
tempest. That work is happening at https://review.openstack.org/#/c/601614/

There was lots of progress made after the last message on this
topic http://lists.openstack.org/pipermail/openstack-dev/2018-September/134837.html
but I've reached another interesting impasse.

>From devstack's standpoint, the way to say "I want to use a tempest
plugin" is to set TEMPEST_PLUGINS to alist of where the plugins are.
devstack:lib/tempest then does a:

     tox -evenv-tempest -- pip install -c $REQUIREMENTS_DIR/upper-constraints.txt $TEMPEST_PLUGINS


I have this part working as expected.


The advice is then to create a new job that has a parent of
devstack-tempest. That zuul job runs a variety of tox environments,
depending on the setting of the `tox_envlist` var. If you wish to
use a `tempest_test_regex` (I do) the preferred tox environment is

That venv doesn't have the plugin installed, thus no gabbi tests are


How do I get my plugin installed into the right venv while still
following the guidelines for good zuul behavior?

Chris Dent                       ٩◔̯◔۶           https://anticdent.org/
freenode: cdent                                         tw: @anticdent

More information about the OpenStack-dev mailing list