[openstack-dev] [Tempest] [Devstack] Where to keep tempest configuration?
boris at pavlovic.me
Thu Mar 17 12:57:49 UTC 2016
There is as well another way to deal with this.
In Rally we have "rally verify" command that you can use to run tempest &
do auto configuration of it.
We can just extend it with new projects, in this case we are simplifying a
lot of life of everybody who wants to use tempest (ops, devops, devs,...)
On Thu, Mar 17, 2016 at 4:50 AM, Jordan Pittier <jordan.pittier at scality.com>
> On Thu, Mar 17, 2016 at 12:24 PM, Vasyl Saienko <vsaienko at mirantis.com>
>> Hello Community,
>> We started using tempest/devstack plugins. They allows to do not bother
>> other teams when Project specific changes need to be done. Tempest
>> configuration is still performed at devstack .
>> So I would like to rise the following questions:
>> - Where we should keep Projects specific tempest configuration?
>> Example 
>> This iniset calls should be made from a devstack-plugin. See 
>> - Where to keep shared between projects tempest configuration?
>> Example 
>> Again, in a devstack plugin. You shouldn't make the iniset call directly
> but instead define some variables in a "setting" file (sourced by
> devstack). Hopefully these variables will be read by lib/tempest (in
> devstack) when the iniset calls will be made. See 
>> As for me it would be good to move Projects related tempest configuration
>> to Projects repositories.
> That's the general idea. It should be possible already right now.
>>  https://github.com/openstack-dev/devstack/blob/master/lib/tempest
>> Thank you in advance,
>> Vasyl Saienko
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev