Re: [openstack-dev] [qa] [tc] [all] more tempest plugins (was Re: [tc] [all] TC Report 22)

2017-06-05 Thread Zane Bitter
On 05/06/17 09:43, Sean Dague wrote: On 06/01/2017 06:09 AM, Chris Dent wrote: It's clear from this thread and other conversations that the management of tempest plugins is creating a multiplicity of issues and confusions: * Some projects are required to use plugins and some are not. This

Re: [openstack-dev] [qa] [tc] [all] more tempest plugins (was Re: [tc] [all] TC Report 22)

2017-06-05 Thread Sean Dague
On 06/01/2017 06:09 AM, Chris Dent wrote: > It's clear from this thread and other conversations that the > management of tempest plugins is creating a multiplicity of issues > and confusions: > > * Some projects are required to use plugins and some are not. This > creates classes of projects.

Re: [openstack-dev] [qa] [tc] [all] more tempest plugins (was Re: [tc] [all] TC Report 22)

2017-06-02 Thread Chris Dent
On Thu, 1 Jun 2017, Matthew Treinish wrote: On Thu, Jun 01, 2017 at 11:09:56AM +0100, Chris Dent wrote: A lot of this results, in part, from there being no single guiding pattern and principle for how (and where) the tests are to be managed. It sounds like you want to write a general testing

Re: [openstack-dev] [qa] [tc] [all] more tempest plugins (was Re: [tc] [all] TC Report 22)

2017-06-01 Thread Matthew Treinish
On Thu, Jun 01, 2017 at 11:09:56AM +0100, Chris Dent wrote: > A lot of this results, in part, from there being no single guiding > pattern and principle for how (and where) the tests are to be > managed. It sounds like you want to write a general testing guide for openstack. Have you started

Re: [openstack-dev] [qa] [tc] [all] more tempest plugins (was Re: [tc] [all] TC Report 22)

2017-06-01 Thread Doug Hellmann
Excerpts from Chris Dent's message of 2017-06-01 11:09:56 +0100: > On Wed, 31 May 2017, Doug Hellmann wrote: > > Yeah, it sounds like the current organization of the repo is not > > ideal in terms of equal playing field for all of our project teams. > > I would be fine with all of the interop

Re: [openstack-dev] [qa] [tc] [all] more tempest plugins (was Re: [tc] [all] TC Report 22)

2017-06-01 Thread Rabi Mishra
On Thu, Jun 1, 2017 at 3:39 PM, Chris Dent wrote: > On Wed, 31 May 2017, Doug Hellmann wrote: > >> Yeah, it sounds like the current organization of the repo is not >> ideal in terms of equal playing field for all of our project teams. >> I would be fine with all of the

Re: [openstack-dev] [qa] [tc] [all] more tempest plugins (was Re: [tc] [all] TC Report 22)

2017-06-01 Thread Chris Dent
On Wed, 31 May 2017, Doug Hellmann wrote: Yeah, it sounds like the current organization of the repo is not ideal in terms of equal playing field for all of our project teams. I would be fine with all of the interop tests being in a plugin together, or of saying that the tempest repo should only

Re: [openstack-dev] [qa] [tc] [all] more tempest plugins (was Re: [tc] [all] TC Report 22)

2017-05-31 Thread Matthew Treinish
On Wed, May 31, 2017 at 03:22:59PM +, Jeremy Stanley wrote: > On 2017-05-31 09:43:11 -0400 (-0400), Doug Hellmann wrote: > [...] > > it's news to me that they're considering reversing course. If the > > QA team isn't going to continue, we'll need to figure out what > > that means and

Re: [openstack-dev] [qa] [tc] [all] more tempest plugins (was Re: [tc] [all] TC Report 22)

2017-05-31 Thread Jeremy Stanley
On 2017-05-31 09:43:11 -0400 (-0400), Doug Hellmann wrote: [...] > it's news to me that they're considering reversing course. If the > QA team isn't going to continue, we'll need to figure out what > that means and potentially find another group to do it. I wasn't there for the discussion, but it

Re: [openstack-dev] [qa] [tc] [all] more tempest plugins (was Re: [tc] [all] TC Report 22)

2017-05-31 Thread Zane Bitter
On 31/05/17 09:43, Doug Hellmann wrote: Excerpts from Chris Dent's message of 2017-05-31 11:22:50 +0100: On Wed, 31 May 2017, Graham Hayes wrote: On 30/05/17 19:09, Doug Hellmann wrote: Excerpts from Chris Dent's message of 2017-05-30 18:16:25 +0100: Note that this goal only applies to

Re: [openstack-dev] [qa] [tc] [all] more tempest plugins (was Re: [tc] [all] TC Report 22)

2017-05-31 Thread Doug Hellmann
Excerpts from Chris Dent's message of 2017-05-31 11:22:50 +0100: > On Wed, 31 May 2017, Graham Hayes wrote: > > On 30/05/17 19:09, Doug Hellmann wrote: > >> Excerpts from Chris Dent's message of 2017-05-30 18:16:25 +0100: > >>> Note that this goal only applies to tempest _plugins_. Projects > >>>

Re: [openstack-dev] [qa] [tc] [all] more tempest plugins (was Re: [tc] [all] TC Report 22)

2017-05-31 Thread Graham Hayes
On 31/05/17 11:22, Chris Dent wrote: > On Wed, 31 May 2017, Graham Hayes wrote: >> On 30/05/17 19:09, Doug Hellmann wrote: >>> Excerpts from Chris Dent's message of 2017-05-30 18:16:25 +0100: Note that this goal only applies to tempest _plugins_. Projects which have their tests in the

[openstack-dev] [qa] [tc] [all] more tempest plugins (was Re: [tc] [all] TC Report 22)

2017-05-31 Thread Chris Dent
On Wed, 31 May 2017, Graham Hayes wrote: On 30/05/17 19:09, Doug Hellmann wrote: Excerpts from Chris Dent's message of 2017-05-30 18:16:25 +0100: Note that this goal only applies to tempest _plugins_. Projects which have their tests in the core of tempest have nothing to do. I wonder if it