Jump to: navigation, search

Difference between revisions of "Rally/Updates"

(May 5th)
(Archives for March 2014)
Line 311: Line 311:
  
 
==== Archives ====
 
==== Archives ====
 +
* [[Rally/UpdatesMarch2014|Weekly updates archives - March 2014]]
 
* [[Rally/UpdatesFebruary2014|Weekly updates archives - February 2014]]
 
* [[Rally/UpdatesFebruary2014|Weekly updates archives - February 2014]]
 
* [[Rally/UpdatesJanuary2014|Weekly updates archives - January 2014]]
 
* [[Rally/UpdatesJanuary2014|Weekly updates archives - January 2014]]
 
* [[Rally/UpdatesDecember2013|Weekly updates archives - December 2013]]
 
* [[Rally/UpdatesDecember2013|Weekly updates archives - December 2013]]
 
* [[Rally/UpdatesNovember2013|Weekly updates archives - November 2013]]
 
* [[Rally/UpdatesNovember2013|Weekly updates archives - November 2013]]

Revision as of 11:20, 5 May 2014

Weekly updates

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:


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 making 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



April 28, 2014

Hello stackers,

the most important changes during the past week in Rally have been concentrated on creating completely new benchmark scenario classes and adding support for new contexts. To be more precise:


This week, we'll continue our work on expanding the range projects supported by our benchmarks. Benchmark scenarios already pending for review are those for Heat, Ceilometer and also Tempest. The ongoing work also includes several improvents in the overall user experience, e.g. changes in the CLI output format.


We encourage you to take a look at new patches in Rally pending for review and to help us making 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



April 21, 2014

Hello stackers,

here is the report of our recent activities in Rally. They have been quite numerous this week due to the contributions of our constantly growing team and include a couple of changes that touch the end user:

  • The scenario runner previously known as continuous has been split to 2 scenario runners named constant and constant_for_duration, thus becoming more "atomic" (previously, the continuous scenario runner was able to run scenarios both for the specified amount of times and for some duration. These two types of behaviour now belong to different runners). "Constant" means that both scenario runners generate a constant load on the cloud;
  • Several changes in the input configuration files formats include:
  • Several improvements in context classes:


This week, we continue our work on new benchmark scenarios for Tempest and quotas, new contexts as well as on many other improvements in Rally.


We encourage you to take a look at new patches in Rally pending for review and to help us making 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



April 14, 2014

Hello stackers,

let us list our main contributions to Rally during the past week:


This week, our work continues with several new benchmark scenarios (including those for Tempest), new validators and also new functionality in the Rally core, e.g. the ability to use already existing tenants/users for benchmarking, implemented now through contexts.


We encourage you to take a look at new patches in Rally pending for review and to help us making 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=icehouse&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



April 7, 2014

Hello stackers,

our contributions this week have been pretty diverse and touched different parts of Rally. Let us name a few that seem to be the most interesting ones:


There are also other parts of Rally which are in progress now and will hopefully have their patches merged the next week, e.g. the work on Tempest integration or further context classes implementation.


We encourage you to take a look at new patches in Rally pending for review and to help us making 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=icehouse&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



March 31, 2014

Hello stackers,

this week, there has been much progress both in the functionality and quality of the Rally code. This has become possible due to the numerous contributions of members of our constantly growing community. The most interesting novelties include:

  • New scenario runner which is called "serial" and enables running scenarios in the same thread as Rally one by one without any concurrency, which makes it easy to debug the benchmark scenarios code;
  • Several contributions to the benchmark scenarios code:
  • NB! We have changed the names of the commonly used DummyEngine and DummyProvider classes to ExistingCloud and ExistingServers, respectively. This has been done in order to improve the readability of deployment configuration files by using more obvious naming.


This week, we concentrate our efforts on diverse work directions that include performance enhancement of the core parts of Rally (as e.g. the UserGenerator context), introducing new benchmark scenarios and finally improving the overall quality of unit tests.


We encourage you to take a look at new patches in Rally pending for review and to help us making 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=icehouse&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



March 24, 2014

Hello stackers,

with great pleasure we've been observing the high rate at which the number of patches pending for review grew over the past week in Rally. Indeed, our community constantly becomes larger and larger (including one new core developer this week), and much more active as well. The highlights of our recent efforts are as follows:


This week, we are going to invest a lot of time in further code refactoring (in a range of areas), as well as in implementing new benchmark scenarios to make Rally applicable for more and more testing use cases.


We encourage you to take a look at new patches in Rally pending for review and to help us making 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=icehouse&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



March 17, 2014

Hello stackers,

the past week has resulted in the further refinement of different parts of Rally code, of its CLI as well as of the configuration file formats. Several of these changes have been caused by the current integration of contexts into Rally (let us remind you that the notion of contexts is used to define different environments in which benchmark scenarios can be launched, e.g. environments with temporarity generated OpenStack users and/or with generic cleanup facilities). Some interesting changes include:


This week, the directions of our efforts are going to be mostly defined by the changes from the refactoring patch mentioned earlier. A lot of stuff has to be rebased, while a couple of deferred important patches (including those implementing support for pre-created users in Rally or introducing the new "stress" scenario running strategy) will be brought to life again.


We encourage you to take a look at new patches in Rally pending for review and to help us making 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=icehouse&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


March 10, 2014

Hello stackers,

over the past week the direction of our efforts hasn't changed significantly: we are still working hard on further logical organization of the core parts of Rally which will enable the system to be even more extendable than it is now. Some important changes include:


This week, we are going to continue the work on the context classes for benchmark scenarios since this is going to be a tool which will make Rally really pluggable. Current tasks include:

  • Changing the benchmark scenario input config format;
  • Splitting the already existing validation procedures to different context classes in a logical way;
  • Implementing the Context class factory (like we did with deploy engines or scenario runners);

and many others.


We are also going to introduce several enhancement both to the task result output (in its HTML form) and to the code (by moving some common code to a special utils module).


We encourage you to take a look at new patches in Rally pending for review and to help us making 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=icehouse&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


March 3, 2014

Hello stackers,

the most important changes during the past week have been concentrated on further logical structuring of the core part of Rally, namely the benchmark engine, and include:


The current direction of our work is the further development of contexts, which will involve introducing new context classes as well.


We encourage you to take a look at new patches in Rally pending for review and to help us making 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=icehouse&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



Archives