Browse code
add TEMPEST_LARGE_OPS_NUMBER to option
The tempest scenario.large_ops test tries to catch any performance issues
when running large numbers of operations at once, in this case launching
instances.
Set to 0 by default, to maintain the current default, but add this as an
option so this can be set via devstacks localrc.
Part of regression test for bug 1199433
Change-Id: I459717b849f9b6d180a7956c0ff470cefe7c1ff6
Joe Gordon authored on 2013/08/27 06:00:05Showing 1 changed files
| ... | ... |
@@ -282,6 +282,9 @@ function configure_tempest() {
|
| 282 | 282 |
# Scenario |
| 283 | 283 |
iniset $TEMPEST_CONF scenario img_dir "$FILES/images/cirros-0.3.1-x86_64-uec" |
| 284 | 284 |
|
| 285 |
+ # Large Ops Number |
|
| 286 |
+ iniset $TEMPEST_CONF scenario large_ops_number ${TEMPEST_LARGE_OPS_NUMBER:-0}
|
|
| 287 |
+ |
|
| 285 | 288 |
# Volume |
| 286 | 289 |
CINDER_MULTI_LVM_BACKEND=$(trueorfalse False $CINDER_MULTI_LVM_BACKEND) |
| 287 | 290 |
if [ $CINDER_MULTI_LVM_BACKEND == "True" ]; then |