Commit Graph

7 Commits

Author SHA1 Message Date
Sergey Skripnick
c72b3dbe31 Expand script path by os.path.expanduser
Make if possible to use tilda in script path

Change-Id: I1dcf32505c86302ebdde41aa2d869665b50f0954
2015-08-14 14:09:14 +02:00
Pavel Boldin
1b2fa45ca8 Make `boot_runcommand_delete' accept command-dict
Make command-executing scenario `boot_runcommand_delete' accepting
command-specifying dict as input. Now `boot_runcommand_delete' is
able to execute a remote command, script from a local file
or inlined one.

Change-Id: I23308922ebae410b1682571c4f114c8080280b19
Implements: blueprint vm-workloads-framework
2015-07-13 17:08:18 +03:00
Christian Berendt
bd37810c5b Remove executable bit from files that should not be executable
Change-Id: I3441ae71dec50277252f462bb8c8e2162dde3aec
2015-05-09 11:49:25 +00:00
Sergey Skripnick
a498c65ed9 Remove sla from Heat scenarios in MOS job
This scenarios is very unstable. Failure rate is much more then 50%

Change-Id: Id3f08b10838d97a3b2db903e635e4b2624e4d880
2015-05-06 14:53:01 +02:00
Kumar Rishabh
758a6c0c42 Add Http Request Scenario
* (сheck-random-request) Add Multiple Http request scenario which
takes as input a list of Requests and compares response of random
picked request from the list with the expected Response.

* (сheck-request) Improve flexiblity of check-response scenario and
rename check-response to check-request.

Co-Authored-By: kumar rishabh <shailrishabh@gmail.com>
Co-Authored-By: Roman Vasilets <rvasilets@mirantis.com>

Change-Id: Id70935616c013271392219b1e642b5b87ddb4b9c
2015-04-28 17:12:37 +00:00
Sergey Skripnick
24178e52da Remove keystone v3 jobs from MOS
There is some issues with MOS and keystone v3
Run all jobs vs keystone v2 endpoints

Change-Id: Ib373251b308c573e0cabc5021c887fa8c8979d56
2015-04-09 12:34:49 +02:00
Sergey Skripnick
eb4d082c60 Add new script for gate jobs
This script will run scenario specified by $RALLY_SCENARIO
environment variable.

Also tags now supported. Tags are stand for modifying
deployment or environment somehow.

Currently implemented only "v3" tag. This tag is changing
deployment endpoints to use keystone v3 protocol.

For example we want to run two scenarios: one for keysone v2
and one for v3. Then we need to create two files:

my-rally.yaml    # will be run vs keystone v2 (v2 is used by default)
my-rally_v3.yaml # will be run vs keystone v3

And export $RALLY_SCENARIO=my-rally.yaml

Change-Id: I44d1788e3892be59afbf8eaecb5d3e3b995fc3a8
2015-02-19 23:23:15 +01:00