openstack/devstack
Code Issues Proposed changes

add TEMPEST_LARGE_OPS_NUMBER to option

Browse Source 
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
This commit is contained in:
Joe Gordon 2013-08-26 17:00:05 -04:00
parent 17be7d5de2
commit bb8c6d42a4
1 changed files with 3 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
lib/tempest
View File

@ -282,6 +282,9 @@ function configure_tempest() {
# Scenario # Scenario
iniset $TEMPEST_CONF scenario img_dir "$FILES/images/cirros-0.3.1-x86_64-uec" iniset $TEMPEST_CONF scenario img_dir "$FILES/images/cirros-0.3.1-x86_64-uec"
# Large Ops Number
iniset $TEMPEST_CONF scenario large_ops_number ${TEMPEST_LARGE_OPS_NUMBER:-0}
# Volume # Volume
CINDER_MULTI_LVM_BACKEND=$(trueorfalse False $CINDER_MULTI_LVM_BACKEND) CINDER_MULTI_LVM_BACKEND=$(trueorfalse False $CINDER_MULTI_LVM_BACKEND)
if [ $CINDER_MULTI_LVM_BACKEND == "True" ]; then if [ $CINDER_MULTI_LVM_BACKEND == "True" ]; then