Re: [openstack-dev] [qa] deprecating Tempest stress framework

2016-02-16 Thread GHANSHYAM MANN
+1 Sounds good to separate those to different repo. Regards Ghanshyam Mann On Wed, Feb 17, 2016 at 4:55 AM, Matthew Treinish wrote: > On Fri, Feb 12, 2016 at 10:21:53AM +0100, Koderer, Marc wrote: >> I know that there are folks around that are using it. >> +1 to move it

Re: [openstack-dev] [qa] deprecating Tempest stress framework

2016-02-16 Thread Matthew Treinish
On Fri, Feb 12, 2016 at 10:21:53AM +0100, Koderer, Marc wrote: > I know that there are folks around that are using it. > +1 to move it to a separate repo. That sounds fine to me, let's mark the stress runner as deprecated and before we remove it someone can spin up a separate repo that owns the

Re: [openstack-dev] [qa] deprecating Tempest stress framework

2016-02-12 Thread Koderer, Marc
I know that there are folks around that are using it. +1 to move it to a separate repo. Regards Marc > On 11 Feb 2016, at 13:59, Daniel Mellado wrote: > > +1 to that, it was my 2nd to-be-deprecated after javelin ;) > > El 11/02/16 a las 12:47, Sean Dague escribió:

[openstack-dev] [qa] deprecating Tempest stress framework

2016-02-11 Thread Sean Dague
In order to keep Tempest healthy I feel like it's time to prune things that are outside of the core mission, especially when there are other options out there. The stress test framework in tempest is one of those. It builds on other things in Tempest, but isn't core to it. I'd propose that

Re: [openstack-dev] [qa] deprecating Tempest stress framework

2016-02-11 Thread Daniel Mellado
+1 to that, it was my 2nd to-be-deprecated after javelin ;) El 11/02/16 a las 12:47, Sean Dague escribió: > In order to keep Tempest healthy I feel like it's time to prune things > that are outside of the core mission, especially when there are other > options out there. > > The stress test