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
* (с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
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