Rally/UpdatesMay2014

May 26, 2014
Hello stackers,

the interesting contributions to Rally during the past week comprise:
 * Yet another set of new benchmark scenarios: this time, for Ceilometer Resources GET API;
 * Documentation for the recently merged plugins functionality (let us remind you that this mechanism enables the developers to extend Rally with new scenarios in an easy way, without actually contributing to the Rally code);
 * There is now a new syntax for marking blocks of benchmark scenarios code that should be timed by Rally as atomic actions (their runtime statistics is available in the detailed results output after benchmarking completes). This syntax is based on the with-clause in Python and enables the developers to write constructs like with AtomicAction(scenario, "name_of_action"): , which tends to be much simpler in many cases that marking entire methods with a special @atomic_action_timer decorator (the previous approach).

This week, our contribution to Rally is going to be continued with new benchmark scenarios (e.g. those for Celiometer Statistics), several refactoring patches (e.g. aimed at somewhat more frequent usage of the Oslo code) and many others.

We encourage you to take a look at new patches in Rally pending for review and to help us make Rally better.

Source code for Rally is hosted at GitHub: https://github.com/stackforge/rally You can track the overall progress in Rally via Stackalytics: http://stackalytics.com/?release=juno&metric=commits&project_type=all&module=rally Open reviews for Rally: https://review.openstack.org/#/q/status:open+rally,n,z

Stay tuned.

Regards, The Rally team

May 19, 2014
Hello stackers,

during the OpenStack Summit in Atlanta we still have accomplished several important contributions to Rally:
 * Another set of new benchmark scenarios in Rally includes those for:
 * Neutron subnets;
 * Ceilometer meters;
 * there is now also a "dummy" scenario which throws an Exception with the given probability, which is very useful for testing purposes.


 * Important bugfixes have been issued for:
 * OpenStack clients usage in cleanup;
 * CLI behaviour in case of a reference to non-existing benchmark task.


 * Finally, pretty much work has been done on code refactoring, such as:
 * unifying the methods for random resource name generation;
 * removing the usage of the deprecated "message" attribute of Exception objects.

Among the most interesting patches being either in progress of ready for review, let's mention more benchmark scenarios for Neutron, Heat and Ceilometer, further improvements in the CLI code, and also the work on the extended input config format which will allow the end-user to put resource names there (e.g. image names to boot servers from) instead of concrete IDs.

We encourage you to take a look at new patches in Rally pending for review and to help us make Rally better.

Source code for Rally is hosted at GitHub: https://github.com/stackforge/rally You can track the overall progress in Rally via Stackalytics: http://stackalytics.com/?release=juno&metric=commits&project_type=all&module=rally Open reviews for Rally: https://review.openstack.org/#/q/status:open+rally,n,z

Stay tuned.

Regards, The Rally team

May 12, 2014
Hello stackers,

here's what has happened in the project during the past week:
 * The list of benchmark scenarios available in Rally "out-of-box" has been extended with new scenarios for Neutron, Ceilometer (Alarms API) and Tempest.
 * There is now a new mechanism for dynamic scenario plugins loading, which enables the developers to extend Rally with new scenarios in an easy way. Note also the docs on how to use plugins in Rally.
 * Overall code improvements include further work on getting rid of the undocumented ThreadPool class, improving logs and others.

Despite the ongoing OpenStack Summit in Atlanta, we still have ambitious plans for this week, which include adding more benchmark scenarios (Heat, Neutron, Ceilometer etc.), working on code runtime efficiency improvements, improving the code for drawing plots and so on.

We encourage you to take a look at new patches in Rally pending for review and to help us make Rally better.

Source code for Rally is hosted at GitHub: https://github.com/stackforge/rally You can track the overall progress in Rally via Stackalytics: http://stackalytics.com/?release=juno&metric=commits&project_type=all&module=rally Open reviews for Rally: https://review.openstack.org/#/q/status:open+rally,n,z

Stay tuned.

Regards, The Rally team

May 05, 2014
Hello stackers,

due to holidays there hasn't been very much contribution to Rally during the past week. The highlights are as follows:
 * Improved CLI output after a benchmark task gets finished. The two tables for atomic actions / overall results now got merged into one very neatly looking table;
 * Several important code improvements include getting rid of the undocumented ThreadPool class and also moving some useful functions for benchmarks data processing into a separate module;
 * New functionality in Rally for this week is the support for the Ironic client (and potentially also for benchmark scenarios for Ironic) and the introduction of Dummy benchmark scenarios that tend to be very useful for developers while testing their changes.

There is going to be much work this week that includes adding new benchmark scenarios (e.g. for Tempest, Neutron and Ceilometer), further improvements in CLI and graphs and also several bugfixes.

We encourage you to take a look at new patches in Rally pending for review and to help us make Rally better.

Source code for Rally is hosted at GitHub: https://github.com/stackforge/rally You can track the overall progress in Rally via Stackalytics: http://stackalytics.com/?release=juno&metric=commits&project_type=all&module=rally Open reviews for Rally: https://review.openstack.org/#/q/status:open+rally,n,z

Stay tuned.

Regards, The Rally team