Rally/RoadMap

Benchmarking

TBD

Context

TBD

Runners

TBD

Scenarios

TBD

Production Read Clean Up

TBD

Non Admin support

TBD

Pre Created Users

TBD

CLI

TBD

Rally-as-a-Service

TBD

Verification

TBD

CI/CD

TBD

Unit & Functional testing

TBD

Data processing

At this moment only thing that we have is getting tables with: min, max, avg. As a first step good=) But we need more!

Data aggregation

to be done...

Graphics & Plots

• Simple plot Time of Loop / Iteration

• Histogram of loop times

Profiling

Improve & Merge Tomograph into upstream

To collect profiling data we use a small library Tomograph that was created to be used with OpenStack (needs to be improved as well). Profiling data is collected by inserting profiling/log points in OpenStack source code and adding event listeners/hooks on events from 3rd party libraries that support such events (e.g. sqlalchemy). Currently our patches are applied to OpenStack code during cloud deployment. For easier maintenance and better profiling results profiler could be integrated as an oslo component and in such case it’s patches could be merged to upstream. Profiling itself would be managed by configuration options.

Improve Zipkin or use something else

Currently we use Zipkin as a collector and visualization service but in future we plan to replace it with something more suitable in terms of load (possibly Ceilometer?) and improve visualization format (need better charts).

Some early results you can see here:

• Terminate 3 VMs
• Run 3 VMs by one request

Make it work out of box

Few things should be done:

1. Merge into upstream Tomograph that will send LOGs to Zipkin
2. Bind Tomograph with Benchmark Engine
3. Automate installation of Zipkin from Rally

Server providing

1. Improve VirshProvider
   1. Implement netinstall linux on VM (currently implemented only cloning existing VM).
   2. Add support zfs/lvm2 for fast cloning
2. Implement LxcProvider
   1. This provider about to be used for fast deployment large amount of instances.
   2. Support zfs clones for fast deployment.
3. Implement AmazonProvider
   1. Get your VMs from Amazon

Deployers

1. Implement MultihostEngine - this engine will deploy multihost configuration using existing engines.
2. Implement Dev FUEL based engine - deploy OpenStack using FUEL on existing servers or VMs
3. Implement Full FUEL based engine - deploy OpenStack with Fuel on bare metal nodes.
4. Implement Tripple-O based engine - deploy OpenStack on bare metal nodes using Tripple-O.