concurrency doesn't work for tests which setup resources in resource_setup

[Vasyl Saienko]

resource_setup() is class method and it is called when tempest is initializing tests. As result --concurrency doesn't take affect.
It is not possible to control concurrency of resources that initiated in resource_setup()

[Jordan Pittier (jordan-pittier)]

What are you suggesting ? :) Have you opened this bug report for information or are you expecting a fix ?

[Vasyl Saienko (vsaienko)]

The way resource_setup realized in tempest doesn't allow to scale it.

I would love to see that tempest uses OptimisingTestSuite from testresources https://pypi.python.org/pypi/testresources

Some working examples may be found here: https://github.com/openstack/oslo.db/blob/master/oslo_db/sqlalchemy/test_fixtures.py#L553-L626

[Jordan Pittier (jordan-pittier)]

Yeah, that looks interesting. Thanks for the pointer.

I am not sure, Tempest should "scale". What does that mean ? If you are talking about overall runtime , then we should measure how much time in spent in resource_setup() vs in actual test code. I don"t want us to start optimizing the wrong part here.

[chandan kumar (chkumar246)]

@vsaienko, Please add some more pointers regarding what does Tempest should "scale" means, so that we can work together to get it done.
@Jordon, setting the flag incomplete in order to get more info from the reporter.

[Launchpad Janitor (janitor)]

[Expired for tempest because there has been no activity for 60 days.]