[openstack-dev] [qa] [Tempest - Stress Test] : some improvements / issues on the stress test framework

LELOUP Julien Julien.LELOUP at 3ds.com
Tue Jan 28 08:40:50 UTC 2014


Hi Marc,

Right I won't forget the [qa] tag anymore :)

Concerning #1273186, actually I wasn't thinking of a change in the CLI, only provide the "kwargs" instance used in "UnitTest" to the stress test scenario during the setUpClass() call.
For now "setUpClass()" is called without any arguments : by calling it this way "setUpClass(**kwargs)" I believe we will be able to provide some configuration parameters in the JSON file stored in "stress/etc/" in the stress test scenario through the "UnitTest" instance.
What do you think ?

I didn't made any code for the two other reports by now, I wanted to get a feedback before doing anything.
Even if I won't have a lot of time to work on Tempest in the near future, I believe these two patches are small enough for me to push and follow them.
I will assign one first and after fighting with Gerrit I will see for getting through the second one :)

Best Regards,

Julien LELOUP
julien.leloup at 3ds.com

-----Original Message-----
From: Koderer, Marc [mailto:m.koderer at telekom.de]
Sent: Monday, January 27, 2014 6:33 PM
To: OpenStack Development Mailing List (not for usage questions)
Cc: LELOUP Julien
Subject: RE: [qa] [Tempest - Stress Test] : some improvements / issues on the stress test framework

Hi Julien,

please don't forget the [qa] tag - otherwise your lost in the ML noise ;)

Ok thanks for the bug reports. I confirmed 1273245 and 1273254 but I am not totally sure with 1273186.
Could you give some more details how the CLI interface will look like? Or simply propose a patch.
It could end up in a quite confusing interface.. if you allow kwargs for such a generic case.

Are you already working on those bugs? If yes, could you assign them to you?

Regards,
Marc

> ________________________________________
> From: LELOUP Julien [Julien.LELOUP at 3ds.com]
> Sent: Monday, January 27, 2014 4:01 PM
> To: openstack-dev at lists.openstack.org
> Subject: [openstack-dev] [Tempest - Stress Test] : some improvements / issues on the stress test framework
>
> Hi everyone,
>
> I would like to discuss some ideas / behavior that seems broken in the stress test part of Tempest.
>
> I opened some tickets in Launchpad and I would like to get the feedback of the community on these ideas / issues :
>
> - Provide kwargs from UnitTest to stress test scenarios (https://bugs.launchpad.net/tempest/+bug/1273186 )
>
> - Stress Test - tearDown() not called if an exception occurred  (https://bugs.launchpad.net/tempest/+bug/1273245 )
>
> - Stress Test - cleanUp() removing all test resources as an admin (https://bugs.launchpad.net/tempest/+bug/1273254 )
>
> Best Regards,
>
> Julien LELOUP
> julien.leloup at 3ds.com
>
>
> This email and any attachments are intended solely for the use of the individual or entity to whom it is addressed and may be confidential and/or privileged.
>
> If you are not one of the named recipients or have received this email in error,
>
> (i) you should not read, disclose, or copy it,
>
> (ii) please notify sender of your receipt by reply email and delete this email and all attachments,
>
> (iii) Dassault Systemes does not accept or assume any liability or responsibility for any use of or reliance on this email.
>
> For other languages, go to http://www.3ds.com/terms/email-disclaimer
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
This email and any attachments are intended solely for the use of the individual or entity to whom it is addressed and may be confidential and/or privileged.

If you are not one of the named recipients or have received this email in error,

(i) you should not read, disclose, or copy it,

(ii) please notify sender of your receipt by reply email and delete this email and all attachments,

(iii) Dassault Systemes does not accept or assume any liability or responsibility for any use of or reliance on this email.

For other languages, go to http://www.3ds.com/terms/email-disclaimer



More information about the OpenStack-dev mailing list