On Thu, Mar 17, 2016 at 12:24 PM, Vasyl Saienko <vsaienko at mirantis.com> wrote: > 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 [0]. > So I would like to rise the following questions: > > > - Where we should keep Projects specific tempest configuration? > Example [1] > > This iniset calls should be made from a devstack-plugin. See [1] > > - Where to keep shared between projects tempest configuration? Example > [2] > > 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 [2] > > - > > 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. > > [0] https://github.com/openstack-dev/devstack/blob/master/lib/tempest > [1] > https://github.com/openstack-dev/devstack/blob/master/lib/tempest#L509-L513 > [2] > https://github.com/openstack-dev/devstack/blob/master/lib/tempest#L514-L523 > > Thank you in advance, > Vasyl Saienko > > [1] https://github.com/openstack/manila/blob/9834c802b8bf565099abf357fe054e086978cf6e/devstack/plugin.sh#L665 [2] https://github.com/openstack/devstack-plugin-ceph/blob/18ee55a0a7de7948c41d066cd4a692e56fe8c425/devstack/settings#L14 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160317/bffa8095/attachment.html>