Rally/UpdatesJune2014
Weekly updates - June 2014
June 23, 2014
Hello stackers,
here is a quick overview of the major contribution in Rally made over the past week:
- New benchmark scenarios:
- Neutron routers API;
- Ceilometer scenario fixes (e.g. the CeilometerBasic scenario group has now been renamed to CeilometerAlarms).
- A quite nice work on code cleanup according to the new hacking 0.9.x requirements has been done to be able to update Rally's global requirements;
- Rally gates have been prepared to be able to run VM scenarios (this work will be finished in the near future).
Current work includes such interesting novelties as the new "stress" scenario runner that generates a growing load until it breaks the cloud, new contexts: Image (boots VMs before benchmarking) and NeutronNetwork (adds pre-created networks) and many others. Also note that there will be soon a large update in the ReadTheDocs Rally page that will make it much more user-oriented.
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
June 16, 2014
Hello stackers,
during the past week, our work has primarily been concentrated on minor bugfixes and enhancements in different parts of Rally. These include:
- Aggregated tables for atomic action runtimes are now available not only in the CLI, but also in the HTML output (generated by the $ rally task plot2html ... command). Let us remind that atomic actions are basic procedures that benchmark scenarios consist of (such as booting a server in Nova or deleting a user in Keystone).
- The docs section of Rally has been extended with the so-called "User stories", which describe use cases of Rally in the real world, some results obtained by Rally as well as their analysis. The first user story is about token creation under different load in Keystone.
- Bugfixes include:
- Fixed installation failure in case pip is not installed on the target system;
- Bugfixes in the quotas context introduce namings corrections and also catching possible errors in the cleanup procedure;
- The constant_for_duration scenario runner now stores results for all the benchmark iterations it has performed, not only for the last ones.
Current work includes such interesting novelties as the new "stress" scenario runner that generated a growing load until it breaks the cloud, the new Image context that boots VMs before benchmarking 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
June 2, 2014
Hello stackers,
one of the most pleasant news for the past week is the appearance of a brand new Rally ReadTheDocs page, where all the docs from the Rally repository are available in a human-readable format.
As for recent patches merged to Rally, so let's pick up the most interesting ones:
- There is now the new Deploy Engine for FUEL (that, as other deploy engines, deploys an OpenStack installation using FUEL and returns endpoints to it).
- A nice refactoring patch has rewritten much CLI code so that it uses more Oslo code.
- Following our good tradition to extend the set of benchmark scenarios available in Rally each week, there are now scenarios for Ceilometer Statistics API.
Among new interesting patches being on their way to Rally, let's mention a filesystem benchmark (that will be launched inside created servers), new context classes for creating images and Neutron networks before launching becnhmarks, 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