openstack/tempest
Code Issues Proposed changes

Remind user about log_level.

Browse Source 
Change-Id: I70284f64769429c2605bde1acd7e741476580316
This commit is contained in:
David Kranz
2012-04-26 15:19:50 -04:00
parent 58a72e8825
commit 73cb6a79af
1 changed files with 8 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
stress/README.rst
View File

@@ -17,7 +17,7 @@ probability that each action should be selected. There are also parameters
controlling rate of fire and stuff like that. controlling rate of fire and stuff like that.
This test framework is designed to stress test a Nova cluster. Hence, This test framework is designed to stress test a Nova cluster. Hence,
you must have a working Nova cluster. you must have a working Nova cluster with rate limiting turned off.
Environment Environment
------------ ------------
@@ -34,12 +34,16 @@ value of --logdir in nova.conf:
controller=<hostname for calling nova-manage> controller=<hostname for calling nova-manage>
max_instances=<limit on instances that will be created> max_instances=<limit on instances that will be created>
Also, make sure to set
log_level=CRITICAL
so that the API client does not log failed calls which are expected while
running stress tests.
The stress test needs the top-level tempest directory to be on PYTHONPATH The stress test needs the top-level tempest directory to be on PYTHONPATH
if you are not using nosetests to run. if you are not using nosetests to run.
For real stress, you need to remove "ratelimit" from the pipeline in
api-paste.ini.
Running the sample test Running the sample test
----------------------- -----------------------