[openstack-dev] [testing] moving testrepository *outside* the tox venv

Robert Collins robertc at robertcollins.net
Sat Jul 11 10:09:17 UTC 2015

On 11 July 2015 at 22:04, Robert Collins <robertc at robertcollins.net> wrote:
> On 11 July 2015 at 12:38, Matthew Treinish <mtreinish at kortar.org> wrote:

>> The whole argument for making testr live outside of the venv and being an
>> implicit dependency like tox is based around tracking the results between the
>> tox venvs right? If we decoupled the database and other result storage from
>> testr a bit and made that the external platform independent piece wouldn't we
>> maintain everything this thread is trying to address without having the issues
>> we're seeing now or requiring that everyone change their usage model and
>> expectations?
> Huh, no.
> The argument is this: a single testr knows how to run heterogeneous
> test backends which may be anywhere in the world, in any language, in
> any context. Running it from within one of those contexts is a
> seriously poor chicken-and-egg situation which doesn't make any sense.
> And the current problem with database compat due to switching out the
> python version between invocations is just the tip of the iceberg.

Oh, I missed a point: the separation of process via subunit from
backend to testr is the heart of the very abstraction of storage etc
you're talking about. We can certainly abstract it further (and making
the glue-in to HTTP repositories better would need that), but its
already there. The issue at hand is that the installation mechanism
for testr within OpenStack's context today is inside-out.


Robert Collins <rbtcollins at hp.com>
Distinguished Technologist
HP Converged Cloud

More information about the OpenStack-dev mailing list