[openstack-dev] [qa] deprecating Tempest stress framework
ghanshyammann at gmail.com
Wed Feb 17 03:08:50 UTC 2016
+1 Sounds good to separate those to different repo.
On Wed, Feb 17, 2016 at 4:55 AM, Matthew Treinish <mtreinish at kortar.org> 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 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 stress runner
> moving forward. But, I don't think we should hold up marking the deprecation
> until that exists. Let's move forward on the deprecation to give users enough
> time to prepare that the in-tree version is going away.
> -Matt Treinish
>> > On 11 Feb 2016, at 13:59, Daniel Mellado <daniel.mellado.es at ieee.org> wrote:
>> > +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 framework in tempest is one of those. It builds on other
>> >> things in Tempest, but isn't core to it.
>> >> I'd propose that becomes deprecated now, and removed in Newton. If there
>> >> are folks that would like to carry it on from there, I think we should
>> >> spin it into a dedicated repository and just have it require tempest.
>> >> -Sean
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
More information about the OpenStack-dev