Difference between revisions of "Rally/RoadMap"
< Rally
(Created page with "= Benchmarking = == Refactor Benchmark Engine == == More scenarios == = Data processing = = Profiling = == Make it work out of box == == Fix or get rid of Zipkin ==...") |
(→Benchmarking) |
||
| Line 1: | Line 1: | ||
| − | = Benchmarking = | + | = Benchmarking Engine= |
| + | |||
| + | == Add support of Users & Tenants out of box == | ||
| + | |||
| + | At this moment we are supporting next 3 parameters: | ||
| + | # timeout - this is the timeout of 1 scenario loop | ||
| + | # times - how much loops of scenario to run | ||
| + | # concurrent - how much loops should be run simultaneously | ||
| + | |||
| + | All tests are run from one user => it is not real situations. | ||
| + | |||
| + | We are going to add two new parameters: | ||
| + | # tenants - how much tenants to create | ||
| + | # users_pro_tenant - how much users should be in each tenant | ||
| + | |||
| + | |||
| + | Benchmark Engine will create all tenants & users, and prepare OpenStack python clients, before starting benchmarking. | ||
| + | |||
| + | == Add generic cleanup mechanism == | ||
| − | |||
== More scenarios == | == More scenarios == | ||
| − | |||
= Data processing = | = Data processing = | ||
Revision as of 01:12, 16 October 2013
Contents
Benchmarking Engine
Add support of Users & Tenants out of box
At this moment we are supporting next 3 parameters:
- timeout - this is the timeout of 1 scenario loop
- times - how much loops of scenario to run
- concurrent - how much loops should be run simultaneously
All tests are run from one user => it is not real situations.
We are going to add two new parameters:
- tenants - how much tenants to create
- users_pro_tenant - how much users should be in each tenant
Benchmark Engine will create all tenants & users, and prepare OpenStack python clients, before starting benchmarking.
