99f165395a
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
31 lines
790 B
JSON
31 lines
790 B
JSON
{% set flavor_name = flavor_name or "m1.tiny" %}
|
|
{
|
|
"NovaKeypair.boot_and_delete_server_with_keypair": [
|
|
{
|
|
"args": {
|
|
"flavor": {
|
|
"name": "{{flavor_name}}"
|
|
},
|
|
"image": {
|
|
"name": "^cirros.*uec$"
|
|
},
|
|
"boot_server_kwargs": {}
|
|
},
|
|
"runner": {
|
|
"type": "constant",
|
|
"times": 5,
|
|
"concurrency": 2
|
|
},
|
|
"context": {
|
|
"users": {
|
|
"tenants": 2,
|
|
"users_per_tenant": 1
|
|
},
|
|
"network": {
|
|
"start_cidr": "100.1.0.0/26"
|
|
}
|
|
}
|
|
}
|
|
]
|
|
}
|