Configure Arguments as Jinja Variables in Sample Task Scenarios
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Rally |
New
|
Undecided
|
Unassigned |
Bug Description
Only a few arguments in Rally sample task scenarios are set as Jinja variable. For consistency and flexibility it would be helpful for most, if not all, of the arguments be changed to Jinja template variables with a default value.
This Nova test has the "image_name" set as a variable at the top.
{% set flavor_name = flavor_name or "m1.tiny" %}
{% set image_name = image_name or "^cirros.*-disk$" %}
This different Nova test does not.
{% set flavor_name = flavor_name or "m1.tiny" %}
If these arguments are changed into variables for every sample task scenario then it also becomes easier for Rally users to combine multiple sample scenarios and only have to supply one (or more) override variable with `--task-args` or `--task-args-file`.
It might even be ideal to set every value as a variable including runner, context, and sla sections.
I totally agree that current approach is far from ideal.
There are few things to take into account:
- Samples were not designed to be used without modifications ... (those are samples)
- We have already pre defined task to get key performance metrics from openstack https:/ /github. com/openstack/ rally/blob/ master/ tasks/openstack _metrics/ task.yaml (and as you can see it's already support bunch of arguments)
- We are going to remove pretty soon samples, because we are working on "rally template" command that is going to allow to store templates in Rally database.
If you have time/will we can work together on template feature that is going to solve all problems above and way more...