[openstack-dev] [qa] RE: [Tempest - Stress Test] : implement a full SSH connection on "ssh_floating.py" and improve it

Koderer, Marc m.koderer at telekom.de
Fri Jan 17 08:45:26 UTC 2014

Hello Juilen,

I forwarded your mail to the correct mailing list. Please do not use the qa list
any longer.

I am happy that you are interested in stress tests. All the tests in
tempest/stress/actions are more or less deprecated. So what you should use
instead is the stress decorator (e.g. https://github.com/openstack/tempest/blob/master/tempest/api/volume/test_volumes_actions.py#L55).
Unfortunately it's not yet used for scenarios like you describe. I'd suggest to
build a scenario test in tempest/scenario and use this decorator on it.

Any patch like that is welcome on gerrit. If you are planning to work in that
area for more than just a patch, a blueprint would be nice. A good way to
coordinate your efforts is also in the QA meeting


From: LELOUP Julien [Julien.LELOUP at 3ds.com]
Sent: Wednesday, January 15, 2014 5:57 PM
To: openstack-qa at lists.openstack.org
Subject: [openstack-qa] [Tempest - Stress Test] : implement a full SSH connection on "ssh_floating.py" and improve it

Hi everyone,

I’m quite new on OpenStack / Tempest and I’m actually working on stress tests. I want to suggest a new feature in a currently available stress test.
Not sure if this email should be posted on the QA mailing list or the dev mailing list, but I give it a try here since it is about a Tempest stress test ☺

At the moment the “ssh_floating.py” stress test seems really interesting but I would like to improve it a bit.

By now this script is simulating an SSH connection by binding a TCP socket on the newly created instance. But this test don’t allow us to check if this instance is really available. I’m mostly thinking about the metadata service unable to provide the SSH key pair to the instance, but surely other scenarios can lead to an instance considered “ACTIVE” but actually unusable.

So I’m implementing a full SSH connection test using the “paramiko” SSH library and a key pair generated in the same way the other test resources are managed in this script : either one SSH key pair for every test runs or a new key pair for each run (depends on the JSON configuration file).
I don’t plan to remove the old test (TCP socket binding), rather move this one on a separate test function and put the full SSH connection test code instead.

Is this feature interesting for the OpenStack community ?
Should I create a blueprint on the Tempest project on Launchpad in order to provide my code through Gerrit ?

On a second time, I plan to overhaul improve this “ssh_floating.py” script by clean the code a little bit, and add more cleaning code in order to avoid leaving instances/security groups/floating IP behind : I do have this kind of behavior right now and I already improved the teardown() on this way.

Should I consider this code as a new functionality (thus create a blueprint) or should I create a defect and assign it to myself ?

Cordialement / Best Regards,


R&D 3DExperience Platform IaaS Factory Technology Engineer

julien.leloup at 3ds.com<mailto:Julien.LELOUP at 3ds.com>

[cid:image003.gif at 01CF1216.D43ECE20]


Dassault Systèmes | 10 rue Marcel Dassault, CS 40501 | 78946 Vélizy-Villacoublay Cedex | France

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