Re: [openstack-dev] [qa][cinder][ceph] should Tempest tests the backend specific feature?

2017-05-03 Thread Matthew Treinish
On Wed, May 03, 2017 at 11:09:32PM -0400, Monty Taylor wrote: > On 05/02/2017 11:49 AM, Sean McGinnis wrote: > > On Tue, May 02, 2017 at 03:36:20PM +0200, Jordan Pittier wrote: > > > On Tue, May 2, 2017 at 7:42 AM, Ghanshyam Mann > > > wrote: > > > > > > > In Cinder,

Re: [openstack-dev] [qa][cinder][ceph] should Tempest tests the backend specific feature?

2017-05-03 Thread Fei Long Wang
On 04/05/17 15:01, Ghanshyam Mann wrote: > > On Wed, May 3, 2017 at 21:57 Andrea Frittoli > > wrote: > > On Tue, May 2, 2017 at 2:41 PM Jordan Pittier > > >

Re: [openstack-dev] [qa][cinder][ceph] should Tempest tests the backend specific feature?

2017-05-03 Thread Ghanshyam Mann
On Wed, May 3, 2017 at 22:35 Sean McGinnis wrote: > On Wed, May 03, 2017 at 01:14:18PM +, Andrea Frittoli wrote: > > > > > > > > > > > Now that this is all in place, I think it's working well and I would > like > > > to see it continue that way. IMO, tempest proper

Re: [openstack-dev] [qa][cinder][ceph] should Tempest tests the backend specific feature?

2017-05-03 Thread Monty Taylor
On 05/02/2017 11:49 AM, Sean McGinnis wrote: On Tue, May 02, 2017 at 03:36:20PM +0200, Jordan Pittier wrote: On Tue, May 2, 2017 at 7:42 AM, Ghanshyam Mann wrote: In Cinder, there are many features/APIs which are backend specific and will return 405 or 501 if same is

Re: [openstack-dev] [qa][cinder][ceph] should Tempest tests the backend specific feature?

2017-05-03 Thread Ghanshyam Mann
On Wed, May 3, 2017 at 21:57 Andrea Frittoli wrote: > On Tue, May 2, 2017 at 2:41 PM Jordan Pittier > wrote: > >> On Tue, May 2, 2017 at 7:42 AM, Ghanshyam Mann >> wrote: >> >>> In Cinder, there are many

Re: [openstack-dev] [qa][cinder][ceph] should Tempest tests the backend specific feature?

2017-05-03 Thread Ghanshyam Mann
On Wed, May 3, 2017 at 21:49 Andrea Frittoli wrote: > On Tue, May 2, 2017 at 6:46 AM Ghanshyam Mann > wrote: > >> In Cinder, there are many features/APIs which are backend specific and >> will return 405 or 501 if same is not implemented on

Re: [openstack-dev] [qa][cinder][ceph] should Tempest tests the backend specific feature?

2017-05-03 Thread Sean McGinnis
On Wed, May 03, 2017 at 01:14:18PM +, Andrea Frittoli wrote: > > > > > > > Now that this is all in place, I think it's working well and I would like > > to see it continue that way. IMO, tempest proper should not have anything > > that isn't universally applicable to real world deployments.

Re: [openstack-dev] [qa][cinder][ceph] should Tempest tests the backend specific feature?

2017-05-03 Thread Andrea Frittoli
On Tue, May 2, 2017 at 4:56 PM Sean McGinnis wrote: > On Tue, May 02, 2017 at 03:36:20PM +0200, Jordan Pittier wrote: > > On Tue, May 2, 2017 at 7:42 AM, Ghanshyam Mann > > wrote: > > > > > In Cinder, there are many features/APIs which are backend

Re: [openstack-dev] [qa][cinder][ceph] should Tempest tests the backend specific feature?

2017-05-03 Thread Andrea Frittoli
On Tue, May 2, 2017 at 2:41 PM Jordan Pittier wrote: > On Tue, May 2, 2017 at 7:42 AM, Ghanshyam Mann > wrote: > >> In Cinder, there are many features/APIs which are backend specific and >> will return 405 or 501 if same is not implemented on

Re: [openstack-dev] [qa][cinder][ceph] should Tempest tests the backend specific feature?

2017-05-03 Thread Andrea Frittoli
On Tue, May 2, 2017 at 6:46 AM Ghanshyam Mann wrote: > In Cinder, there are many features/APIs which are backend specific and > will return 405 or 501 if same is not implemented on any backend [1]. > If such tests are implemented in Tempest, then it will break some gate

Re: [openstack-dev] [qa][cinder][ceph] should Tempest tests the backend specific feature?

2017-05-02 Thread Jeremy Stanley
On 2017-05-02 10:49:55 -0500 (-0500), Sean McGinnis wrote: [...] > > So basically, if one of the 50 Cinder driver doesn't support a > > feature, we should never test that feature ? What about the 49 > > other drivers ? If a feature exists and can be tested in the > > Gate (with whatever default

Re: [openstack-dev] [qa][cinder][ceph] should Tempest tests the backend specific feature?

2017-05-02 Thread Sean McGinnis
On Tue, May 02, 2017 at 03:36:20PM +0200, Jordan Pittier wrote: > On Tue, May 2, 2017 at 7:42 AM, Ghanshyam Mann > wrote: > > > In Cinder, there are many features/APIs which are backend specific and > > will return 405 or 501 if same is not implemented on any backend

Re: [openstack-dev] [qa][cinder][ceph] should Tempest tests the backend specific feature?

2017-05-02 Thread Eric Harney
On 05/02/2017 01:42 AM, Ghanshyam Mann wrote: > In Cinder, there are many features/APIs which are backend specific and > will return 405 or 501 if same is not implemented on any backend [1]. > If such tests are implemented in Tempest, then it will break some gate > where that backend job is

Re: [openstack-dev] [qa][cinder][ceph] should Tempest tests the backend specific feature?

2017-05-02 Thread Jordan Pittier
On Tue, May 2, 2017 at 7:42 AM, Ghanshyam Mann wrote: > In Cinder, there are many features/APIs which are backend specific and > will return 405 or 501 if same is not implemented on any backend [1]. > If such tests are implemented in Tempest, then it will break some gate

[openstack-dev] [qa][cinder][ceph] should Tempest tests the backend specific feature?

2017-05-01 Thread Ghanshyam Mann
In Cinder, there are many features/APIs which are backend specific and will return 405 or 501 if same is not implemented on any backend [1]. If such tests are implemented in Tempest, then it will break some gate where that backend job is voting. like ceph job in glance_store gate. There been many