We have a lot of validators for scenarios, but we do not check input
arguments. There are two cases:
1) user forget specify some argument;
2) user specify redundant argument
In both cases, we will get "TypeError" for each iteration.
This validator is not implemented like others, since it doesn't need
constructed clients and it looks like more syntax check.
Also, this patch fixes one of our samples:
samples/tasks/scenarios/dummy/dummy-random-action.[json/yaml]
Change-Id: Id3aad571dfc93f8074c724595440979cfd435e2c
The scenario first creates a volume and creates a
snapshot from this volume, then boots a server from
the created snapshot.
Change-Id: Ib2a320ab097ac05c104729223cc4ae1e53365144
In function create_nested_snapshots_and_attach_volume, nested_level's
default value is 1, and it is used to operate with an integer
(for i in range(nested_level - 1):).
Change-Id: I4879d7cdcb5a56b83a1415c4a8fc427241ddc913
Closes-Bug: #1594656
Scenario VMTasks.boot_runcommand_delete now can populate
report tab "Scenario Data" with any allowed charts.
SSH command return value structure new reflects
Scenario.add_output() arguments.
Also, there is new shell script
samples/tasks/support/instance_test.sh which generates
different load on server and creates proper JSON output.
Old format of command output is also supported but marked
as deprecated.
Change-Id: I6a34b634ea7d9080f9ca08bf0f82d04fa69406d9
Add the argument "auto_assign_nic: true" in boot_and_delete_server
functional test, and add a related sample.
Change-Id: I7e596c29ae5e9d9c6e7db4572b5e80a60f0dd0bb
1:Add nested_level argument for nested cloning volume to new volume.
2:Fix the bug that new volume assiged size is possibly less than
source volume size when setting size argument "min: 1, max: 5".
Change-Id: I18ae333189423461bca52f783311bcf43354ccab
I think it is better to add the argument image to create_and_upload_volume_to_image.
Now possibly upload a empty volume to image, it is meaningless to the business.
Closes-Bug: #1582117
Change-Id: Ie10d17a422fb5b1635dd8d6d7e235e7327843f17
Murano scenario list_environments just measures time of API call
at this moment because there are no environments created by default.
To fix it new context has been added to make possible generate
Murano environments before Rally iterations.
Change-Id: Ide0c928fd608503f4916f84d81c942c0ce5fec28
For the moment all users for tasks are taken randomly and
there is no way to balance them between tasks.
It may be very useful when we have
difference between first usage of tenant/user and all consecutive.
In this case we get different load results.
Therefore, add enum config option 'user_choice_method'
to 'users' context that defines approach for picking up users.
Two values are available:
- random
- round_robin
Default one is compatible with old approach - "random".
Also, update one of scenarios to use "round_robin" approach to make
sure it works.
Change-Id: I26fb090eb89c22f5d50529cb73b6ed54fc3d7e15
Benchmark create-flavor and flavor-access-list
Nova API.
blueprint extend-api-benchmark-in-nova-scenarios
Change-Id: I870405aaaec727cfb3a0b460dcf60c6a7ca4b6d1
* add heat template validator to the validators.
* add `template_validator` to each Heat scenario with usage of templates
* add missed sla section to some scenarios in mos job
* fix samples - allow them to work from the box
Change-Id: I33aa709a3c4b94cb48c8067df685eee6442c0210
Closes-bug: #1535948
This adds a plugin to collect the avg time duration for each
atomic action. With this, SLAs setting time maximums can be
applied to individual atomic actions that are part of a run.
For example:
NeutronNetworks.create_and_list_ports:
-
sla:
max_avg_duration_per_atomic:
neutron.list_ports: 5.5
This would put a 5.5 second limit on the average amount of
time spent listing ports. During the create_and_list_ports
test run.
This allows projects to put more fine-grained restrictions
on different types of operations (e.g. GET vs POST).
Change-Id: I752a53ae3b2f47a05057ad8d4688f3f74d75ecf0
Current patch contains 4 scenarios from heat repo:
- output-show for old algorithm
- output-show for new algorithm
- output-list for old algorithm
- output-list for new algorithm
The patch includes samples and unittests.
Co-Authored-By: Sergey Kraynev <skraynev@mirantis.com>
Change-Id: I37f0ac3f1ddb7cd6d7ea21753b28cebe9ffd754a
Generate atomic actions with random durations.
This scenario is suitable for demonstration of upcoming
trends report (will be introduced in further patches)
Change-Id: I46207c2d7db848f923820fcc499c46d3c8ecb855
With this configuration you can test heat caching.
Already was in heat repo, just added it to rally.
Change-Id: I8bd35a0f96a9f73a33f434ad7e3412db6f1d95ad
When running a scenario, `kwargs` is used as default key-word arguments.
But in some scenarios, there are more and one services being called, and
we use xxx_kwargs for this case.
However, some xxx_kwargs are not unifed for same usage[0]. Unifying
these could avoid midleading for end users. Another improvement is to
add xxx_kwargs with empty settings for scenario config files.
[0] http://paste.openstack.org/show/489505/
Change-Id: I80f49be5c1cd21812d6b2d56b0f4279f0cf4f402
VM task scenarios executes a script with a interpreter provided through
a formatted argument called 'command' which expects the remote_path or local_path
of the script and optionally an interpreter with which the script has to be
executed.
Change-Id: If2e65b553a0f26180267ef0b8e2239e3efe4ea17
Add create_and_(list|delete)_recordset scenarios
Remove the test also that checks the allowed methods, this is in order for us
to be able to have a private method _walk_pages that will do fetching of pages
for us vs attempting to fetch 1 giant list at once.
Change-Id: I43b111ebe07f3842fce48af4898978130d1341d7
Add support for listing nova hosts, agents, availability-zones
and aggregates.
blueprint extend-api-benchmark-in-nova-scenarios
Change-Id: I1facd17719299128e758334b468c01a83518889e
Seems like this feature is broken and not used.
Remove module fuel from deployment engines.
Remove package fuel from deployment.
Remove fuel samples.
Remove unittests relative to fuel engine.
Change-Id: I54c1a5de2028a667c35d3b6038c69a64a866451c
The flavors for Master and Worker node groups is now configured
separatelly in both scenarios and context.
This allows setting up better balanced clusters when a Master node
may require a bigger flavor than workers. This is almost always a
requirement for plugins like CDH or HDP.
Change-Id: I78f4145fecb327dae06ead02bd1aa85e2ba2b79a
This patch adds support for providing additional arguments to
create_volume in the rally task CinderVolumes.create_and_attach_volume.
Currently only the size of the volume to be created can be given.
Change-Id: I9c7ca61629c817ad44d2421a1fe988c75140c6e5
Closes-Bug: #1522935
This finally takes new output format into use by two main changes:
* Reworking and refactoring of HTML report frontend, mainly in
template rally/ui/templates/task/report.html, so we have
the following new features and improvements:
- show output in new format, according to the spec
- Added AngularJS directive (via attribute `widget')
that can render all currently used NVD3 charts,
and generic HTML tables
- all existent charts (as well as new output charts) and
generic tables are displayed by our new AngularJS directive
- Fix: do not show StackedArea if there are less than 2 points
- code optimization and rafactoring
* New scenario `Dummy.dummy_output' is added, so we can
generate random output in new format to see how it is
displayed in reports.
Change-Id: Ifa30e6ec86217898fbd6133eaa3e3552f466bf26
This submission adds create_and_update_domain method to
rally/benchmark/scenarios/designate/basic.py.
Adds update method to "utils.py" under
"rally/benchmark/scenarios/designate".
Added configuration files for designate update-domain
operation under samples/tasks/scenarios/designate.
1) create-and-update-domain.json
2) create-and-update-domain.yaml
Also added unit tests to 'test_basic.py' and 'test_utils.py'
under 'rally/tests/unit/plugins/openstack/scenarios/designate'.
Change-Id: I58468666c0eb73143a0a451466ba41d12a9076d6
