The list of services that Tempest used to set its 'service_available'
config values was hard-coded. To be plugin-friendly have each
service (project) add its name to the TEMPEST_SERVICES variable
and use that for setting the 'service_avilable' values.
Change-Id: I208efd7fd0798b18ac2e6353ee70b773e84a2683
The tempest api.volume.test_volume_types test won't
work with non-default drivers configured for cinder's backend
any more. The reason is that we create a type using capability
scheduler keywords in the extra-specs for the test;
(vendor_name and storage_protocol). The result is the extra-spec
uses the filters: "vendor_name=Open Source" and
"storage_protocol=iSCSI", but for example if you have another backend
say SolidFire, EMC, NetApp, IBM etc the capabilities filter will fail
the create with a "No valid host available".
This is intended to work by simply setting these values in your
tempest.conf file. That's fine, however upon setting this up
in my localrc I found that the tempest config variables being
set via devtsack were never picked up
Currently devstack doesn't use the same variable names for
configuration variables as tempest expects. Devstack is using
the variable "TEMPEST_CONF" however the Tempest project is
expecting the variable "TEMPEST_CONFIG", so currently the
devstack lib/tempest rc variables are never picked up by
tempest properly.
This change modifes devstack's naming of TEMPEST_CONF, my though
being that since this doesn't work in devstack currently
that changing it here would be better than changing it in Tempest
where it's possible people had their own custoizations already
outside of devstack.
In addition this change creates rc variables in devstack to actually
set these via devstack. The idea here is that Cinder 3'rd party testing
needs to be a simple devstack config and run stack.sh. By fixing up
the configuration file variable naming and adding the variables for
the vendor and protocol settings that's now possible.
An example localrc for a custom config is shown below. The example
sets the tempest config file to /etc/tempest/tempest.conf, and
configures tempest to use the SolidFire driver as the cinder backend.
TEMPEST_VOLUME_VENDOR ==> tempest.conf.volume_vendor
TEMPEST_STORAGE_PROTOCOL ==> tempest.conf.storage_protocol
relevant example localrc entries:
TEMPEST_CONFIG=/etc/tempest/tempest.conf
TEMPEST_CONFIG_DIR=/etc/tempest
TEMPEST_VOLUME_DRIVER=solidfire
TEMPEST_VOLUME_VENDOR="SolidFire Inc"
***NOTE***
storage_protocol and vendor_name MUST match what the backend device reports from
get capabilities.
Change-Id: I28dfa90c877b27f5d4919f2748fae092bb2f87fa
Closes-Bug: 1271781
This patch adds queuing to tempest config, provided queuing is
available in devstack.
Change-Id: I2925a07d312c1f8ab2fe465f74f0bef9299eef40
Implements: blueprint add-basic-marconi-tests
This patch introduces a Devstack variable to specify which network
extensions are enabled; this is useful for configuring tempest runs
when third-party plugins that do not support certain extensions.
Closes-bug: #1247778
Closes-bug: #1231152
Change-Id: Iee170993cb164502774f9ac4201b963d9a2715ba
If $HEAT_FETCHED_TEST_IMAGE is set then tempest is configured to
use the image named $HEAT_FETCHED_TEST_IMAGE for any orchestration
tests which require an image.
Fallback to checking $HEAT_CREATE_TEST_IMAGE and invoking
diskimage-builder if necessary.
The intent is to use Fedora 20 as the test image for gating
since this image has heat-cfntools already installed.
Change-Id: I177ae091a641ba99fd4c618e30a39c5148ae617f
The default nano and micro flavors need more memory to boot on
ppc64. New flavors are 128MB and 256MB, respectively.
Trailing spaces removed, again.
Change-Id: Ic6740bda959754380982e67f753876dc6d984685
With this patch, the public network config in tempest.conf will be
done for the plugins that support L3.
Change-Id: I820fe300fac45ff92d1281ff0c43ebc137783210
* lib/tempest: When creating the m1.tiny and m1.nano flavors ensure that
they don't exist first. This is important for Grenade where code may be
run multiple times and should expect that some things preexist.
Change-Id: I1772d4334f39d612f8a187eb5311a1b2caee3953
In order to run tempest tests for Ironic in devstack
the availability of the Ironic service must be set in
the tempest config.
This patch adds a shortcut for Ironic services and sets
availability of Ironic in tempest config.
Change-Id: I206fc2ea13412ceb128f8bfe90c153348d6f2f3e
Address miscellaneous issues with Markdown formatting in comments which
are consumed by shocco when generating the online documentation.
Change-Id: I953075cdbddbf1f119c6c7e35f039e2e54b79078
The run_ssh option is used on the default 'false',
so several test case and validation step was disabled.
It was disabled because:
* Admin password injection with the cirros image is not supported.
(We 'cannot' inject password/shadow to a ram disk.)
* In the current system setup floating IP is required for connecting
with neutron
The run_ssh boolean option will be removed from tempest, it will be replaced
with ssh_connect_method and ssh_auth_method.
Since using a floating ip with nova flat network is not required in these
case, the 'fixed'/private IPs (ssh_connect_method) will be used with nova network
, and we will use the 'floating' IPs with neutron when the NAMESPACES
are enabled(default).
The default value of ssh_auth_method is keypair, it works in both cases.
Change-Id: I3d47811d801985687526749a430ed6db64224f99
The BUILD_TIMEOUT is the generally used timeout option in tempest.
Almost never expected to any operation takes more than 60 sec,
the 400 sec is too match for timeout.
Changing the BUILD_TIMEOUT to 196 sec, it is still expected to be safe.
It can make faster the failing test jobs.
Change-Id: I7e7c767400ca448cb86d27b60a1229a2afa69726
This reverts commit 3d84cf2d7c323750971cf2d27f3a4eaa26cb7a9f.
This is believed to be the cause for the massive increase in
neutron failures in the gate reseting other projects. Realize
this is just a work around.
Change-Id: Id3c59f3fe9ccbb869eb3200ef7ff2659409e2253
Partial-Bug: 1224001
This commit re-enables tenant isolation in tempest for neutron. This
is a requirement for running tempest in parallel. This commit depends
on tempest change I7587c85017cca09f7a67eae0670f67b2bceacb60
Fixes bug 1216076
Change-Id: I63a30bacd48cecd110fb90e1fc718249c2b1904b
this will set to True the tempest volume/volume_backup_enabled
option if c-bak is in ENABLED_SERVICES
Change-Id: I69931d668411fc8144d0fdb2f58ad9b6e987f793
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 requires HEAT_CREATE_TEST_IMAGE to be set for any images
to be created.
If the file (files/fedora-vm-heat-cfntools-tempest.qcow2) already
exists then disk-image-create will not be called, and the existing
image file will be registered with glance. This is most likely to
happen in the following scenarios:
- a second run of stack.sh
- the image has been pre-built elsewhere (such as during devstack-gate
image building)
Change-Id: I276573a20927e72f2cb68784f655c1ba1913ae8a
With tempest moving to testr (serially currently) the log level is no
longer defaulting to debug as it did with nose. To get the same level
of verbosity in the logging as when running with nose this commit
sets the debug flag on tempest.
Change-Id: I6acd57be0f8188d31825d88471ba9883ebb30519
This commit will correctly set the tempest output logging to dump
all of tempest logs into a tempest.log file in
$DEST/tempest/tempest.log. This will also fix the logging for
tempest in the gate so it will no longer print every log message on
the console.
Fixes bug 1207066
Change-Id: I91f2ee781c4a7a18c561ea3e3b26832b97431464
Change I464edf9e11710e1931ed4f7b0262328a57e5b3de set the tempest
lock_path to be $TMPDIR, however when run in the gate this is an
empty string which results in all tests that use locking failing.
This commit corrects that by setting the lock_path config variable
to use $TEMPEST_STATE_PATH which defaults to $DATA_DIR/tempest.
Change-Id: I02fbd50ca68d6daafb5b4c23579473eb703ae72a
Tempest change I5376f977a110f502f0e4958cbccbd379539e006b syncs
lockutils from oslo. Tempest with testr needs to use external locks
which require a lock_path config option. This commit sets that option
for tempest to use devstack's TMPDIR.
Change-Id: I464edf9e11710e1931ed4f7b0262328a57e5b3de
This commit loops over the list of services that tempest has config
options for in the service_available group and checks if the service
is enabled. Devstack will then set whether or not the service is
configured in tempest.conf.
Change-Id: Ib845d3e098fd3f45c8c26f5696af14cca1534e01
Tempest change I5ee9ec816845de483fe88d76d1bb047e7bb1af7e changed
the behavior of the neutron_available config option. This commit
updates devstack to use it's new name and group.
Change-Id: I7d5074209fe81f6100f380512d7702fbc8e252ac
The default value does not work unless devstack is installed in
/opt/stack/new/devstack. This patch changes the img_dir option to point
to the correct install location.
Change-Id: Iea41d209dad10b2f9a7c97efd55c39a8d29347cc
