Difference between revisions of "Rally/Updates"

Latest revision as of 12:02, 22 January 2015

Updates

January 22, 2014

Hi stackers!

We are happy to announce that we have completely redesigned our Rally documentation in ReadTheDocs. The docs have now received a simpler structure and have become much easier to get through!

One of the nicest new things is the Rally step-by-step tutorial that explains, in a series of lessons, how to explore the power of Rally in benchmarking your OpenStack clouds.

Since our previous update, there have been many interesting updates in Rally:

Rally now has a Network Context class that enables easy Neutron network management.
Input task files now can be written using the jinja2-based templates syntax. Very useful if you want, say, parameterize the image name used throughout your complex input task file.
Rally scenarios have been 100%-covered with docstrings. That means that now the rally info find <query> command will always output a complete piece information about whatever you ask it.
New benchmark scenarios include thos for Cinder (list_volumes, list_snapshots, extend_volume), Nova (cold_migrate)
We have moved the directory with samples in our repository to the root level: now it is rally/samples instead of rally/doc/samples (and so much quicker to get to).
Rally is on the way to being Python 3 compatible. We have added a Gate job that checks Rally in Python 3 and have produced lots of patches that fix incompability issues. Few changes are left to make Rally fully Python 3 compatible.

Current work includes new benchmark scenarios (Mistral, Murano), new success criteria (SLA) and a lot of refactoring in scenario runners, Rally API etc.

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=kilo&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

December 15, 2014

Hi stackers!

Let us share with you our recent accomplishments in Rally:

CLI improvements:

The rally info command (which is a kind of built-in Rally reference) has been enhanced in such a way that it now prints detailed explanations of main concepts used in Rally whenever you type something like rally info BenchmarkScenarios or rally info SLA. We've also improved the output formatting so that now it is much easier to get through.
The rally task list command now supports filters. You can filter the task list either by deployment (using the "... --deployment <deployment_name_or_id>" parameter) or by status ("... --status <status_name>")

New benchmark scenarios:

NovaSecGroup.boot_and_delete_server_with_secgroups: creates a number of Nova security groups with rules, then creates a Neutron network with one subnet, finally boots a VM with created security groups, lists the created resources and performs cleanup.
CinderVolumes.create_nested_snapshots_and_attach_volume: creates a volume, its snapshot, and then (recursively) a volume from that snapshot. The recursion depth can be set by the user through the --nested_level parameter.

Other improvements:

Work on Trove support in Rally has been started with the integration of its client;
New hacking rules are there to provide better codestyle throughout Rally.

Current work is centered aroud code refactoring (both major, as in the benchmark engine or the contexts, and minor, as introducing some syntax sugar via decorators to mark deprecated stuff and scenario samples). We also constantly work on expanding our scenario base. Last but not least, we're about to merge the Network Context class that enables easy Neutron network management.

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=kilo&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

December 1, 2014

Hi stackers!

It's been a while since our last post here, and we've done quite a nice job in Rally during November. Let us share with you new things about Rally:

Autogenerated HTML benchmark reports in Rally (which can be created by the "rally task report" command after a benchmark task has completed) have been improved further within the last month. As of now, the report page contains an overview table, detailed informations about whether SLA (service-level agreement) checks were successful and also detailed error logs, if any. Rally reports have become a wonderful tool indeed to analyse the benchmarking data as well as to share your results with others!
Similar improvements have been made for HTML reports generated for the Tempest cloud verification ("rally verify results --html --output_file <file>"). New enhanced report pages have improved styling and refactored JS code.
We have changed the way context classes in Rally should be declared. Having introduced a new @context decorator, we've made it much easier and also more readable.
There is a new "servers" context that allows you to create temporary servers before benchmark scenarios start and use these servers for testing inside these scenarios.
New benchmark scenarios in Rally include those for Nova live migrate and also a Cinder stress scenario.
Command-line interface improvements include an ability to refer deployments not only by uuid but also by name. Please note that the syntax has changed a bit so now you have to supply the --deployment parameter to commands like "rally use deployment" (instead of --uuid).
There has been some major refactoring of the most critical parts of Rally code: the cleanup mechanism and the "users" context code. We are sure that after refactoring, this code has become both cleaner and less error-prone (as well as very pluggable in the case of cleanups).

Current work includes further code refactoring (e.g. in the Benchmark engine part), further CLI improvements (e.g. for the "rally task list" command) and also new benchmark scenarios (e.g. for Murano). We are also going to introduce a possibility of building Rally images for Docker.

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=kilo&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

October 27, 2014

Hello stackers,

much time has passed since our last update and we are happy to announce that we are moving towards making our first official Rally release! Our active recent contribution to Rally has enabled us to make a significant progress. Here are the highlights of the novelties in Rally:

We have completely redesigned the auto-generated benchmark report page so that it looks now even nicer than before and is much more easy to navigate. Besides, further improvements of this HTML report page are on their way to being merged soon.
Rally now has an extended support of plugins: in addition to writing custom scenarios, the plugin mechanism now enables to extend Rally with new context classes/scenario runners without actually contributing to the Rally master branch.
The work on extending the support of OpenStack projects in Rally has been conducted for Heat and Sahara.
CLI improvements: the command-line interface gets more and more user-friendly over time: recently, it has begun to support detailed informations about correct commands usage in case of a failure. The "rally info" command has also been improved so that it now supports misspellings handling. Finally, there has been some work on bash completion, which hasn't been completely finished yet.
Test code improvements: we have greatly proceeded in out continuous work on unit/functional test coverage improvement. We also have moved all the tests into a special tests/ directory so that the test code is now organized in a more neat way. We also have removed the ./run_tests.sh script for the sake of using the tox command to launch the test suite.

In the nearest future, several interesting refactoring patches are going to come to Rally. To be more specific, there will be a vast change of the benchmark engine and cleanup mechanisms.

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=kilo&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

September 26, 2014

Hello stackers,

here is a brief overview of what has happened in Rally recently:

We have refactored the code responsible for atomic actions processing in Rally benchmarks. Let's remind you that each benchmark scenario in Rally consists of a series of atomic actions, whereas the running time of each atomic action is measured in the same way as that of the whole scenario. After refactoring, we now ensure that Rally doesn't skip atomic actions that failed and distinguishes different runs of two atomic actions with the same name (see an example of how a typical results table could look before and looks after refactoring).
Another direction of refactoring was the SLA code; it has been modified so that now SLA results are stored in the DB along with other benchmarking data.
Check out a nice user story about VMs boot performance in Nova with Rally. It shows how Rally can be used in practice to catch reals bugs and improve OpenStack performance.
We work hard on achieving 100% test coverage in Rally: last week, additional unit tests for contexts and scenarios have been merged.

Our current priorities are further refactoring steps, including those in critical parts of Rally (e.g. temporary user creation and cloud cleanup code); we also strive towards making Rally bug-free and continuously issue different bugfixing patches.

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

September 15, 2014

Hello stackers,

there has been much diverse and useful contribution to Rally recently. Let us highlight some interesting updates in our project:

Rally is on its way to support of benchmarking OpenStack clouds using ordinary user accounts that already exist. Rally lacked such functionality (it only supported benchmarking either from an admin account or from a bunch of temporarily created users), which posed a problem since some deployments don't allow temporary users creation. There have been two patches that prepare the code for this new functionality. It is going to come very soon - stay tuned.
We constantly improve our gate jobs (jobs that run a test suite for every patch pending review in Rally). Recently, we have introduced a nice aggregated results page for that gate job (see an example). It now makes it very easy for developers to navigate through the results of tests agains their patches to Rally.
We have added a new "volumes" context which makes it possible to create cinder volumes in the benchmark environment and use them later in the actual benchmark scenarios.
Much work has been accomplished on the overall code quality improvement. We have both made several code refactoring patches and introduced several new test suites (say, functional tests for CLI).

Current work centers around introducing benchmarking with pre-created users as mentioned above; much work is currently devoted to new benchmark scenarios as well. Also please note that there will be soon an important update on Rally ReadTheDocs page, which will make it much easier to navigate and get through, especially for newbies.

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

September 1, 2014

Hello stackers,

over the past week, Rally has been extended with the following features:

Rally now offers a pretty simple feature request mechanism. Everyone who is interested in adding new functionality to Rally now can share his ideas in a standartized format (see an example). All you need to do is to write down your feature request in a separate rst-file in the doc/feature_request folder and submit it as a patch to Rally (if you are unsure about how to do this, read our "How to contribute" tutorial).
We added a new benchmark scenario for Cinder quotas creation/deletion.
Designate support in Rally has been extended so that it is posisble now to set up Designate quotas.

There is pretty much work going on this week, including the introduction of benchmarking with existing users (in addition to those created temporarily, which was the only option before), and also improvements in the plugin mechanism, so that it will be possible now to write plugins for runners and contexts. We do lots of code refactoring and will do even more in the upcoming weeks.

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

August 25, 2014

Hello stackers,

here is a quick overview of what has been added to Rally recently:

Rally now supports Designate, which is a DNaaS service for OpenStack (providing REST API for domain/record management). Several new bechmark scenarios for Designate have been added as well;
In the CLI, we have added a new command called rally info. It is a essentially a special search engine embedded into Rally, which, for a given search query, prints documentation for the corresponding benchmark scenario/deploy engine/... as fetched from the source code. Thus you can learn about different Rally entities without leaving the Command Line Interface. For usage samples, see this link;
We have extended the SLA output which indicates whether a benchmark has passed some set of predefined success criteria with customizable messages;
We have performed a range of nice optimizations:

The main work directions for the next week comprise further improvement in the contexts mechanism (both the algorithm of context creation and new context classes), further optimizations (e.g., multithreaded objects deletion) and also code refactoring (e.g., of that for tracking atomic actions in benchmark scenarios)

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

August 4, 2014

Hello stackers,

below you will find the most recent updates in Rally:

The periodic scenario runner has been refactored and renamed, as of now, to rpc (runs per second). Note that this renaming also affects task configuration files that use that runner type. The runner itself now has been reimplemented with the multiprocessing.Process class (instead of multiprocessing.Pool), which potentially decreases memory usage on large iterations and reduces errors.
A nice optimization to the chart generation code ensures that the Rally plots will be rendered fast in browsers even for tasks with a huge number of iterations completed.
New benchmark scenarios include those testing the Nova server resize operation and a set of benchmarks for Sahara group node templates.
We continue extending our gates with nice features. A new one are the SLA checks that add information about whether benchmark scenarios pass a set of success criteria (see an example)

Many interesting improvements are on their path to being merged to Rally. Among them, let us mention the "rally info" command, which prints descriptions for different entities in Rally to the console, further work on the Rally documentation which gets cleaner and cleaner, and also a set of new context classes, including those for generating images for VM benchmarks, as well as for creating Neutron networks.

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

July 17, 2014

Hello stackers,

here are some recent updates in Rally:

Results of scenario runners are now stored asynchronously. This is precondition for such further features like piecemeal storing of results to DB (to reduce RAM usage), or progress displaying.
Add check if required services are available before starting the scenario. This is realized by adding services validation to scenarios. Also this patch includes new validation mechanism.
Ability to cancel task by keyboard interrupts is availiable now;
Add base to provide interation testing;
A lot of of patches to improve unit tests coverage.

This week, our work continues with such main novelties as adding support for Keystone API v3, adding context classes for avoiding vm creation if tenant has no network and prepare an image that will have installed the required programs, mechanism to provide rally as a service, code refactoring in context manager to make code more clear.

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

July 07, 2014

Hello stackers,

here is the update for the last weeks. From all the work we've completed we would like to highlight the following:

New benchmark scenarios:

Benchmark to validate a keystone token N times at service endpoint that allows to check effect of caching related to tokens;
Scenario for benchmark Neutron ports.

Add nova floating ip management in VM scenario, before this patch the VM runcommand scenario used the fixed ip to ssh connect to the instance, this could only worked if fixed ip range was directly accessible with was the case in very limited deployments.
Add image context class that allows adding images to each user for benchmarks, also this patch provides scenario which tests glance image-list command;
Large update of documentation that simplifies its index structure and headings, extends the 'Benchmark' page with info from the "Main concepts" and adds some introductory text on Deploy & Verify parts;
Add service-level agreement checking that allows to add section in task configuration that contains the criteria of success, e.g "less then 5% of failure rate", or "faster then 5 seconds for one iteration";
Use oslo.db module and remove rally/openstack/common/db.

Current work includes such interesting novelties as context semantic validation, periodic runner refactoring, "rally info" command which prints descriptions for different entities in Rally, checking if required services are available before starting the scenario and refactoring of validation system, continue work on "stress" runner.

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

Difference between revisions of "Rally/Updates"

Latest revision as of 12:02, 22 January 2015

Contents

Updates

January 22, 2014

December 15, 2014

December 1, 2014

October 27, 2014

September 26, 2014

September 15, 2014

September 1, 2014

August 25, 2014

August 4, 2014

July 17, 2014

July 07, 2014

Archives

@@ Line 1: / Line 1: @@
-== Weekly updates ==
+== Updates ==
-==== June 23, 2014 ====
+==== January 22, 2014 ====
-Hello stackers,
+Hi stackers!
-here is a quick overview of the major contribution in Rally made over the past week:
+We are happy to announce that we have completely redesigned our [http://rally.readthedocs.org/en/latest/ Rally documentation in ReadTheDocs]. The docs have now received a simpler structure and have become much easier to get through!
-* New benchmark scenarios:
+One of the nicest new things is the [http://rally.readthedocs.org/en/latest/tutorial.html Rally step-by-step tutorial] that explains, in a series of lessons, how to explore the power of Rally in benchmarking your OpenStack clouds.
-:* [https://review.openstack.org/92873 '''Neutron''' routers API];
-:* [https://review.openstack.org/96365 '''Ceilometer'''] scenario fixes (e.g. the ''CeilometerBasic'' scenario group has now been renamed to ''CeilometerAlarms'').
-* A quite nice work on [https://review.openstack.org/100599 '''''code cleanup''''' according to the new '''hacking 0.9.x''' requirements] has been done to be able to [https://review.openstack.org/102135 update Rally's global requirements];
-* Rally gates have been [https://review.openstack.org/#/c/100563/ prepared to be able to run VM scenarios] (this work will be finished in the near future).
+Since our previous update, there have been many interesting updates in Rally:
+* Rally now has a [https://review.openstack.org/103306 Network Context class] that enables easy Neutron network management.
+* Input task files now can be written using the [https://review.openstack.org/137716 jinja2-based templates syntax]. Very useful if you want, say, parameterize the image name used throughout your complex input task file.
+* Rally scenarios have been [https://review.openstack.org/127192 100%-covered with docstrings]. That means that now the '''rally info find <query>''' command will always output a complete piece information about whatever you ask it.
+* New benchmark scenarios include thos for '''Cinder''' ([https://review.openstack.org/142500 list_volumes], [https://review.openstack.org/146580 list_snapshots], [https://review.openstack.org/147489 extend_volume]), '''Nova''' ([https://review.openstack.org/148307 cold_migrate])
+* We have [https://review.openstack.org/147412 moved] the directory with samples in our repository to the root level: now it is ''rally/samples'' instead of ''rally/doc/samples'' (and so much quicker to get to).
+* Rally is on the way to being '''Python 3 compatible'''. We have added a Gate job that checks Rally in Python 3 and have produced [https://review.openstack.org/144706 lots] [https://review.openstack.org/144971 of] [https://review.openstack.org/145450 patches] [https://review.openstack.org/145492 that] [https://review.openstack.org/141163 fix] [https://review.openstack.org/144185 incompability] [https://review.openstack.org/144143 issues]. Few changes are left to make Rally fully Python 3 compatible.
-Current work includes such interesting novelties as [https://review.openstack.org/94806 the new '''"stress"''' scenario runner] that generates a growing load until it breaks the cloud, new contexts: [https://review.openstack.org/#/c/95353/ '''Image'''] (boots VMs before benchmarking) and [https://review.openstack.org/96300 '''NeutronNetwork'''] (adds pre-created networks) and many others. Also note that there will be soon a large [https://review.openstack.org/99304 update] in the [http://rally.readthedocs.org/en/latest/ ReadTheDocs Rally page] that will make it much more user-oriented.
+Current work includes new benchmark scenarios ([https://review.openstack.org/144320 Mistral], [https://review.openstack.org/137650 Murano]), [https://review.openstack.org/148079 new success criteria (SLA)] and a lot of refactoring in scenario runners, Rally API etc.
-We encourage you to take a look at new patches in Rally pending for review and to help us make Rally better.
+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<br/>
-You can track the overall progress in Rally via Stackalytics: http://stackalytics.com/?release=juno&metric=commits&project_type=all&module=rally <br/>
+You can track the overall progress in Rally via Stackalytics: http://stackalytics.com/?release=kilo&metric=commits&project_type=all&module=rally <br/>
 Open reviews for Rally: https://review.openstack.org/#/q/status:open+rally,n,z
-Stay tuned.
+Stay tuned!
@@ Line 32: / Line 35: @@
-==== 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 [https://review.openstack.org/#/c/97710/ '''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).
+==== December 15, 2014 ====
-* The '''docs''' section of Rally has been extended with the so-called [https://review.openstack.org/95144 '''"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:
+Hi stackers!
-:* [https://review.openstack.org/#/c/98677/ '''Fixed installation failure'''] in case ''pip'' is not installed on the target system;
-:* [https://review.openstack.org/#/c/99441/ Bugfixes in the '''quotas context'''] introduce namings corrections and also catching possible errors in the cleanup procedure;
-:* [https://review.openstack.org/98989 The '''constant_for_duration''' scenario runner] now stores results for all the benchmark iterations it has performed, not only for the last ones.
+Let us share with you our recent accomplishments in Rally:
+* '''CLI improvements:'''
+:* The '''''rally info''''' command (which is a kind of built-in Rally reference) has been [https://review.openstack.org/#/c/131005/ enhanced] in such a way that it now prints detailed explanations of main concepts used in Rally whenever you type something like '''''rally info BenchmarkScenarios''''' or '''''rally info SLA'''''. We've also improved the output formatting so that now it is much easier to get through.
+:* The '''''rally task list''''' command now [https://review.openstack.org/131005 supports] '''filters'''. You can filter the task list either by deployment (using the ''"... --deployment <deployment_name_or_id>"'' parameter) or by status (''"... --status <status_name>"'')
+* '''New benchmark scenarios:'''
+:* [https://review.openstack.org/#/c/129282 '''''NovaSecGroup.boot_and_delete_server_with_secgroups''''']: creates a number of Nova security groups with rules, then creates a Neutron network with one subnet, finally boots a VM with created security groups, lists the created resources and performs cleanup.
+:* [https://review.openstack.org/#/c/139019/ '''''CinderVolumes.create_nested_snapshots_and_attach_volume''''']: creates a volume, its snapshot, and then (recursively) a volume from that snapshot. The recursion depth can be set by the user through the ''--nested_level'' parameter.
+* '''Other improvements''':
+:* Work on '''Trove support in Rally''' has been started with the [https://review.openstack.org/139047 integration of its client];
+:* New [https://review.openstack.org/139022 '''hacking rules'''] are there to provide better codestyle throughout Rally.
-Current work includes such interesting novelties as [https://review.openstack.org/94806 the new '''"stress"''' scenario runner] that generated a growing load until it breaks the cloud, [https://review.openstack.org/#/c/95353/ the new '''Image''' context] that boots VMs before benchmarking and many others.
+Current work is centered aroud code refactoring (both major, as in the '''benchmark engine''' or the [https://review.openstack.org/139987 '''contexts'''], and minor, as introducing some syntax sugar via '''decorators''' to mark [https://review.openstack.org/138489 deprecated stuff] and [https://review.openstack.org/140033 scenario samples]). We also constantly work on expanding our [https://review.openstack.org/141672 scenario] [https://review.openstack.org/136922 base]. Last but not least, we're about to merge the [https://review.openstack.org/103306 Network Context class] that enables easy Neutron network management.
-We encourage you to take a look at new patches in Rally pending for review and to help us make Rally better.
+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<br/>
-You can track the overall progress in Rally via Stackalytics: http://stackalytics.com/?release=juno&metric=commits&project_type=all&module=rally <br/>
+You can track the overall progress in Rally via Stackalytics: http://stackalytics.com/?release=kilo&metric=commits&project_type=all&module=rally <br/>
 Open reviews for Rally: https://review.openstack.org/#/q/status:open+rally,n,z
-Stay tuned.
+Stay tuned!
@@ Line 63: / Line 70: @@
-==== June 2, 2014 ====
-Hello stackers,
-one of the most pleasant news for the past week is the appearance of a brand new [http://rally.readthedocs.org/en/latest/ 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:
+==== December 1, 2014 ====
-* There is now [https://review.openstack.org/61963 '''the new Deploy Engine for FUEL'''] (that, as other [https://wiki.openstack.org/wiki/Rally/DeployEngines deploy engines], deploys an OpenStack installation using [https://wiki.openstack.org/wiki/Fuel FUEL] and returns endpoints to it).
+Hi stackers!
-* A nice [https://review.openstack.org/94143 '''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 [https://review.openstack.org/94143 '''Ceilometer Statistics API'''].
+It's been a while since our last post here, and we've done quite a nice job in Rally during November. Let us share with you new things about Rally:
+* '''Autogenerated HTML benchmark reports''' in Rally (which can be created by the '''''"rally task report"''''' command after a benchmark task has completed) have [https://review.openstack.org/#/c/131844/ been] [https://review.openstack.org/#/c/136435/ improved] further within the last month. As of now, the [http://logs.openstack.org/05/131005/28/check/gate-rally-dsvm-rally/f8f3da9/rally-plot/results.html.gz report page] contains an overview table, detailed informations about whether [http://logs.openstack.org/05/131005/28/check/gate-rally-dsvm-rally/f8f3da9/rally-plot/results.html.gz#/Authenticate.validate_cinder SLA (service-level agreement) checks] were successful and also detailed error logs, if any. Rally reports have become a wonderful tool indeed to analyse the benchmarking data as well as to share your results with others!
+* Similar improvements have been made for HTML reports generated for the '''Tempest cloud verification''' ('''''"rally verify results --html --output_file <file>"'''''). New [https://review.openstack.org/#/c/135232/ enhanced] report pages have improved styling and refactored JS code.
+* We have [https://review.openstack.org/#/c/137502/ changed] the way '''context classes''' in Rally should be declared. Having introduced a new '''''@context''''' decorator, we've made it much easier and also more readable.
+* There is a new '''[https://review.openstack.org/127392 "servers" context]''' that allows you to create temporary servers before benchmark scenarios start and use these servers for testing inside these scenarios.
+* '''New benchmark scenarios''' in Rally include those for '''[https://review.openstack.org/128631 Nova live migrate]''' and also a '''[https://review.openstack.org/127392 Cinder stress scenario]'''.
+* '''Command-line interface improvements''' include an ability to [https://review.openstack.org/131463 refer deployments not only by uuid but also by name]. Please note that the syntax has changed a bit so now you have to supply the ''--deployment'' parameter to commands like ''"rally use deployment"'' (instead of ''--uuid'').
+* There has been some '''major refactoring''' of the most critical parts of Rally code: the [https://review.openstack.org/129060 cleanup mechanism] and the [https://review.openstack.org/119297 "users" context code]. We are sure that after refactoring, this code has become both cleaner and less error-prone (as well as very pluggable in the case of cleanups).
-Among new interesting patches being on their way to Rally, let's mention [https://review.openstack.org/97030 a '''filesystem benchmark''' (that will be launched inside created servers)], new '''context classes''' for creating [https://review.openstack.org/95353 images] and [https://review.openstack.org/96300 Neutron networks] before launching becnhmarks, and many others.
+Current work includes further code refactoring (e.g. in the ''Benchmark engine'' part), further CLI improvements (e.g. for the [https://review.openstack.org/131005 "rally task list" command]) and also new benchmark scenarios (e.g. for [https://review.openstack.org/137661 Murano]). We are also going to introduce a possibility of building Rally images for [https://review.openstack.org/#/c/132556/ Docker].
-We encourage you to take a look at new patches in Rally pending for review and to help us make Rally better.
+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<br/>
-You can track the overall progress in Rally via Stackalytics: http://stackalytics.com/?release=juno&metric=commits&project_type=all&module=rally <br/>
+You can track the overall progress in Rally via Stackalytics: http://stackalytics.com/?release=kilo&metric=commits&project_type=all&module=rally <br/>
 Open reviews for Rally: https://review.openstack.org/#/q/status:open+rally,n,z
-Stay tuned.
+Stay tuned!
@@ Line 95: / Line 105: @@
-==== May 26, 2014 ====
+==== October 27, 2014 ====
 Hello stackers,
-the interesting contributions to Rally during the past week comprise:
+much time has passed since our last update and we are happy to announce that we are moving towards making our first official Rally release! Our active recent contribution to Rally has enabled us to make a significant progress. Here are the highlights of the novelties in Rally:
-* '''Yet another set of new benchmark scenarios''': this time, for [https://review.openstack.org/90203 Ceilometer Resources GET API];
+* We have completely '''[https://review.openstack.org/125119 redesigned] the auto-generated benchmark report page''' so that it looks now even nicer than before and is much more easy to navigate. Besides, further improvements of this HTML report page are on their way to being merged soon.
-* [https://review.openstack.org/92364 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);
+* Rally now has an extended support of '''[https://review.openstack.org/103145 plugins]''': in addition to writing custom scenarios, the plugin mechanism now enables to extend Rally with new context classes/scenario runners without actually contributing to the Rally master branch.
-* There is now a [https://review.openstack.org/#/c/92800/ 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"): <do_smth>'', which tends to be much simpler in many cases that marking entire methods with a special '''@atomic_action_timer''' decorator (the previous approach).
+* The work on extending the support of OpenStack projects in Rally has been conducted for '''[https://review.openstack.org/128874 Heat]''' and '''[https://review.openstack.org/126900 Sahara]'''.
+* '''CLI improvements''': the command-line interface gets more and more user-friendly over time: recently, it has begun to support [https://review.openstack.org/124910 detailed] informations about correct commands usage in case of a failure. The ''"rally info"'' command has also been improved so that it now supports '''[https://review.openstack.org/125238 misspellings handling]'''. Finally, there has been some work on '''[https://review.openstack.org/129306 bash completion]''', which hasn't been completely finished yet.
+* '''Test code improvements''': we have greatly proceeded in out continuous work on unit/functional test coverage improvement. We also have [https://review.openstack.org/126379 moved] all the tests into a special ''tests/'' directory so that the test code is now organized in a more neat way. We also have removed the ''./run_tests.sh'' script for the sake of using the ''tox'' command to launch the test suite.
-This week, our contribution to Rally is going to be continued with new benchmark scenarios (e.g. those for [https://review.openstack.org/91320 Celiometer Statistics]), several refactoring patches (e.g. aimed at [https://review.openstack.org/94143 somewhat more frequent usage of the Oslo code]) and many others.
+In the nearest future, several interesting refactoring patches are going to come to Rally. To be more specific, there will be a vast change of the benchmark engine and cleanup mechanisms.
-We encourage you to take a look at new patches in Rally pending for review and to help us make Rally better.
+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<br/>
-You can track the overall progress in Rally via Stackalytics: http://stackalytics.com/?release=juno&metric=commits&project_type=all&module=rally <br/>
+You can track the overall progress in Rally via Stackalytics: http://stackalytics.com/?release=kilo&metric=commits&project_type=all&module=rally <br/>
 Open reviews for Rally: https://review.openstack.org/#/q/status:open+rally,n,z
@@ Line 123: / Line 135: @@
+==== September 26, 2014 ====
-==== May 19, 2014 ====
 Hello stackers,
-during the OpenStack Summit in Atlanta we still have accomplished several important contributions to Rally:
+here is a brief overview of what has happened in Rally recently:
-* Another set of '''new benchmark scenarios''' in Rally includes those for:
+* We have [https://review.openstack.org/111977 refactored] the code responsible for '''atomic actions processing''' in Rally benchmarks. Let's remind you that each benchmark scenario in Rally consists of a series of atomic actions, whereas the running time of each atomic action is measured in the same way as that of the whole scenario. After refactoring, we now ensure that Rally '''doesn't skip atomic actions that failed''' and '''distinguishes different runs of two atomic actions with the same name''' (see an example of how a typical results table could look [http://paste.openstack.org/show/114111/ before] and looks [http://paste.openstack.org/show/114112/ after] refactoring).
-:* [https://review.openstack.org/91350 '''''Neutron''''' subnets];
+* Another direction of refactoring was the [https://review.openstack.org/118243 SLA code]; it has been modified so that now SLA results are '''stored in the DB''' along with other benchmarking data.
-:* [https://review.openstack.org/#/c/90331/ '''''Ceilometer''''' meters];
+* Check out a nice [https://github.com/stackforge/rally/blob/master/doc/user_stories/nova/boot_server.rst user story] about '''VMs boot performance''' in Nova with Rally. It shows how Rally can be used in practice to catch reals bugs and improve OpenStack performance.
-:* there is now also a [https://review.openstack.org/91679 "dummy" scenario] which throws an ''Exception'' with the given probability, which is very useful for testing purposes.
+* We work hard on achieving '''100% test coverage''' in Rally: last week, additional unit tests for [https://review.openstack.org/122127 contexts] and [https://review.openstack.org/122729 scenarios] have been merged.
-* Important '''bugfixes''' have been issued for:
-:* [https://review.openstack.org/#/c/93413/ OpenStack clients usage] in cleanup;
-:* [https://review.openstack.org/89998 CLI behaviour] in case of a reference to non-existing benchmark task.
-* Finally, pretty much work has been done on '''code refactoring''', such as:
-:* [https://review.openstack.org/93586 unifying the methods for random resource name generation];
-:* [https://review.openstack.org/93575 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 [https://review.openstack.org/92873 '''''Neutron'''''], [https://review.openstack.org/86431 '''''Heat'''''] and [https://review.openstack.org/90203 '''''Ceilometer'''''], [https://review.openstack.org/90005 further] [https://review.openstack.org/94143 improvements] in the CLI code, and also the work on the [https://review.openstack.org/86116 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.
+Our current priorities are further '''refactoring''' steps, including those in critical parts of Rally (e.g. [https://review.openstack.org/119297 temporary user creation] and [https://review.openstack.org/116269 cloud cleanup] code); we also strive towards making Rally bug-free and continuously issue different bugfixing patches.
 We encourage you to take a look at new patches in Rally pending for review and to help us make Rally better.
@@ Line 159: / Line 163: @@
+==== September 15, 2014 ====
-==== May 12, 2014 ====
 Hello stackers,
-here's what has happened in the project during the past week:
+there has been much diverse and useful contribution to Rally recently. Let us highlight some interesting updates in our project:
-* The list of benchmark scenarios available in Rally "out-of-box" has been extended with new scenarios for [https://review.openstack.org/88537 '''''Neutron'''''], [https://review.openstack.org/88216 '''''Ceilometer''''' ''(Alarms API)''] and [https://review.openstack.org/86836 '''''Tempest'''''].
+* Rally is on its way to support of '''benchmarking OpenStack clouds using ordinary user accounts that already exist'''. Rally lacked such functionality (it only supported benchmarking either from an admin account or from a bunch of temporarily created users), which posed a problem since some deployments don't allow temporary users creation. There have been [https://review.openstack.org/#/c/116766/ two] [https://review.openstack.org/#/c/119344/ patches] that prepare the code for this new functionality. It is going to come very soon - stay tuned.
-* There is now a new mechanism for [https://review.openstack.org/72679 dynamic '''''scenario plugins''''' loading], which enables the developers to extend Rally with new scenarios in an easy way. Note also the [https://review.openstack.org/#/c/92364/ docs] on how to use plugins in Rally.
+* We constantly improve our '''gate jobs''' (jobs that run a test suite for every patch pending review in Rally). Recently, we have [https://review.openstack.org/#/c/119584/ introduced] a nice aggregated results page for that gate job (see an [http://logs.openstack.org/84/119584/13/gate/gate-rally-dsvm-rally/d30c028/ example]). It now makes it very easy for developers to navigate through the results of tests agains their patches to Rally.
-* Overall code improvements include further work on [https://review.openstack.org/91398 getting rid of the undocumented ThreadPool class], [https://review.openstack.org/93276 improving logs] and others.
+* We have [https://review.openstack.org/116446 added] a new '''"volumes" context''' which makes it possible to create cinder volumes in the benchmark environment and use them later in the actual benchmark scenarios.
+* Much work has been accomplished on the overall code quality improvement. We have both made several code refactoring patches and introduced several new test suites (say, [https://review.openstack.org/118714 functional tests for CLI]).
-Despite the ongoing OpenStack Summit in Atlanta, we still have ambitious plans for this week, which include adding more benchmark scenarios ([https://review.openstack.org/86431 '''''Heat'''''], [https://review.openstack.org/91350 '''''Neutron'''''], [https://review.openstack.org/90331 '''''Ceilometer'''''] etc.), working on [https://review.openstack.org/93413 code runtime efficiency improvements], improving the [https://review.openstack.org/91680 code for drawing plots] and so on.
+Current work centers around introducing benchmarking with pre-created users as mentioned above; much work is currently devoted to new benchmark scenarios as well. Also please note that there will be soon an important update on [http://rally.readthedocs.org/en/latest/ Rally ReadTheDocs page], which will make it much easier to navigate and get through, especially for newbies.
 We encourage you to take a look at new patches in Rally pending for review and to help us make Rally better.
@@ Line 188: / Line 191: @@
+==== September 1, 2014 ====
-==== 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:
+over the past week, Rally has been extended with the following features:
-* [https://review.openstack.org/89941 Improved '''CLI output'''] after a benchmark task gets finished. The two tables for atomic actions / overall results now got merged into [http://paste.openstack.org/show/77630/ one very neatly looking table];
+* Rally now offers a pretty simple [https://review.openstack.org/#/c/116403/ '''feature request''' mechanism]. Everyone who is interested in adding new functionality to Rally now can share his ideas in a standartized format ([https://github.com/stackforge/rally/blob/master/doc/feature_request/historical_performance_data.rst see an example]). All you need to do is to write down your feature request in a separate ''rst-file'' in the ''doc/feature_request'' folder and submit it as a patch to Rally (if you are unsure about how to do this, read our [[Rally/Develop#How_to_contribute|"How to contribute" tutorial]]).
-* Several important code improvements include [https://review.openstack.org/89375 getting rid of the undocumented ThreadPool class] and also [https://review.openstack.org/89526 moving some useful functions for benchmarks data processing into a separate module];
+* We added a new benchmark scenario for [https://review.openstack.org/#/c/115929/ '''Cinder quotas''' creation/deletion].
-* New functionality in Rally for this week is [https://review.openstack.org/87603 the support for the '''Ironic''' client] (and potentially also for benchmark scenarios for Ironic) and the introduction of [https://review.openstack.org/89219 '''Dummy''' benchmark scenarios] that tend to be very useful for developers while testing their changes.
+* Designate support in Rally has been extended so that it is posisble now to set up [https://review.openstack.org/#/c/116852/ '''Designate quotas'''].
-There is going to be much work this week that includes adding new benchmark scenarios (e.g. for [https://review.openstack.org/92022 Tempest], [https://review.openstack.org/88537 Neutron] and [https://review.openstack.org/88216 Ceilometer]), further improvements in CLI and graphs and also several bugfixes.
+There is pretty much work going on this week, including the introduction of [https://review.openstack.org/116766 benchmarking with existing users] (in addition to those created temporarily, which was the only option before), and also improvements in the [https://review.openstack.org/103145 plugin mechanism], so that it will be possible now to write plugins for runners and contexts. We do lots of code refactoring and will do even more in the upcoming weeks.
 We encourage you to take a look at new patches in Rally pending for review and to help us make Rally better.
@@ Line 216: / Line 217: @@
+==== August 25, 2014 ====
-==== 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:
+here is a quick overview of what has been added to Rally recently:
-* We've added benchmark scenarios that [https://review.openstack.org/86337 launch '''Tempest''' tests] and check the performance of [https://review.openstack.org/#/c/87283/ updating '''quotas for nova/cinder''']. Both are quite new to Rally and allow users to compose more interesting benchmark cases.
+* Rally now [https://review.openstack.org/#/c/116405/ supports] '''Designate''', which is a ''DNaaS service'' for OpenStack (providing REST API for domain/record management). Several new [https://github.com/stackforge/rally/tree/master/doc/samples/tasks/scenarios/designate bechmark scenarios for Designate] have been added as well;
-* There is one new context, the [https://review.openstack.org/87984 '''''"roles"''''' context] that allows to change user roles before using those users in benchmark scenarios. Much work has also been done on [https://review.openstack.org/90579 refactoring the '''''"cleanup"''''' context] and helper methods that it uses.
+* In the CLI, we have added a new command called [https://review.openstack.org/102853 '''rally info''']. It is a essentially a special '''search engine''' embedded into Rally, which, for a given search query, prints '''documentation''' for the corresponding benchmark scenario/deploy engine/... as fetched from the source code. Thus you can learn about different Rally entities without leaving the Command Line Interface. For usage samples, see [https://wiki.openstack.org/wiki/Rally/HowTo#Available_Rally_facilities this link];
-* We've [https://review.openstack.org/89988 integrated the new '''''oslotest''''' library], wich allowed us to remove much of the "common openstack" code from our repository.
+* We have [https://review.openstack.org/#/c/113253/ extended the SLA output] which indicates whether a benchmark has passed some set of predefined success criteria with customizable messages;
+* We have performed a range of nice '''optimizations''':
+:* [https://review.openstack.org/#/c/114839/ Reduced gate jobs runtime];
-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 [https://review.openstack.org/#/c/86431/ '''''Heat'''''], [https://review.openstack.org/#/c/88216/ '''''Ceilometer'''''] and also [https://review.openstack.org/86836 '''''Tempest''''']. The ongoing work also includes several improvents in the overall user experience, e.g. changes in the [https://review.openstack.org/89941 CLI output format].
+:* [https://review.openstack.org/#/c/104962/ Code clarification in the context manager];
+:* [https://review.openstack.org/#/c/116014/ Gates tests fixing].
+The main work directions for the next week comprise further improvement in the contexts mechanism (both [https://review.openstack.org/116045 the algorithm of context creation] and [https://review.openstack.org/116446 new context classes]), further optimizations (e.g., [https://review.openstack.org/113536 multithreaded objects deletion]) and also code refactoring (e.g., of that for [https://review.openstack.org/111977 tracking atomic actions in benchmark scenarios])
 We encourage you to take a look at new patches in Rally pending for review and to help us make Rally better.
@@ Line 245: / Line 246: @@
+==== August 4, 2014 ====
-==== 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:
+below you will find the most recent updates in Rally:
-* The scenario runner previously known as '''''continuous''''' [https://review.openstack.org/#/c/83316/ 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;
+* The '''periodic scenario runner''' has been [https://review.openstack.org/#/c/102363/ refactored and renamed], as of now, to '''rpc''' (runs per second). Note that this renaming also affects task configuration files that use that runner type. The runner itself now has been reimplemented with the ''multiprocessing.Process'' class (instead of ''multiprocessing.Pool''), which potentially decreases memory usage on large iterations and reduces errors.
-* Several changes in the input configuration files formats include:
+* A nice [https://review.openstack.org/#/c/106031/ optimization to the '''chart generation code'''] ensures that the Rally plots will be rendered fast in browsers even for tasks with a huge number of iterations completed.
-:* [https://review.openstack.org/#/c/88493/ Renaming the '''''"name"''''' attribute of deployments to '''''"type"'''''] in the deployment configuration file. The same change now also applies to [https://review.openstack.org/#/c/88648/ server providers];
+* '''New benchmark scenarios''' include those testing the [https://review.openstack.org/#/c/109915 Nova server resize] operation and a set of benchmarks for [https://review.openstack.org/#/c/107962 Sahara group node templates].
-:* [https://review.openstack.org/#/c/89309/ Renaming the '''''"active_users"''''' attribute of the constant scenario runners to '''''"concurrency"'''''] in the benchmark task configuration files.
+* We continue '''extending our gates''' with nice features. A new one are the [https://review.openstack.org/#/c/111347/ SLA checks] that add information about whether benchmark scenarios pass a set of success criteria (see an [http://logs.openstack.org/47/111347/5/gate/gate-rally-dsvm-rally/a14f11b/rally-plot/sla.txt example])
-* Several '''''improvements in context classes''''':
-:* Fixing a couple of issues with the  '''''cleaner context''''': [https://review.openstack.org/#/c/87761 incorrect context initialization] and [https://review.openstack.org/#/c/87764 buggy cleanup of Glance resources];
-:* [https://review.openstack.org/#/c/89292/ Improving the '''''user context'''''] by making it create the temporary users in concurrent mode by default.
-* '''''New benchmark scenarios''''' include those for [https://review.openstack.org/#/c/86267/ '''''Keystone tenants and users listing'''''];
-This week, we continue our work on new benchmark scenarios for [https://review.openstack.org/#/c/86337/ '''''Tempest'''''] and [https://review.openstack.org/#/c/87283/ '''''quotas'''''], new [https://review.openstack.org/#/c/87984/ '''''contexts'''''] as well as on many other improvements in Rally.
+Many interesting improvements are on their path to being merged to Rally. Among them, let us mention the [https://review.openstack.org/#/c/102853 "rally info" command], which prints descriptions for different entities in Rally to the console, further work on the [https://review.openstack.org/110738 Rally documentation] which gets cleaner and cleaner, and also a set of new context classes, including those for [https://review.openstack.org/#/c/104564/ generating images] for VM benchmarks, as well as for creating [https://review.openstack.org/#/c/96300/ Neutron networks].
 We encourage you to take a look at new patches in Rally pending for review and to help us make Rally better.
@@ Line 279: / Line 273: @@
+==== July 17, 2014 ====
+Hello stackers,
-==== April 14, 2014 ====
+here are some recent updates in Rally:
-Hello stackers,
+* Results of scenario runners [https://review.openstack.org/#/c/104518 are now stored asynchronously]. This is precondition for such further features like piecemeal storing of results to DB (to reduce RAM usage), or progress displaying.
+* Add [https://review.openstack.org/#/c/97556 check if required services are available] before starting the scenario. This is realized by adding services validation to scenarios. Also this patch includes new validation mechanism.
+* Ability to [https://review.openstack.org/#/c/103145/3 cancel task by keyboard interrupts] is availiable now;
+* Add base to provide [https://review.openstack.org/#/c/102899 interation testing];
+* A lot of of patches to improve [https://review.openstack.org/#/q/status:merged+project:stackforge/rally+branch:master+topic:bp/improve-unit-test-coverage-rally,n,z unit tests coverage].
-let us list our main contributions to Rally during the past week:
-* The [https://review.openstack.org/#/c/85732/ '''''Bechmark context manager class'''''], which mostly finishes the work on contexts integration in Rally; this manager allows Rally to use only those contexts that are really needed for the current benchmark scenario, thus greatly reducing the runtime of the preparation step, manages the order of entering those contexts, adds logging for contexts and does a couple of other important things;
-* Improvement of the CLI for the '''''Tempest verifier''''': we've added [https://review.openstack.org/#/c/85584/ '''''the functionality of saving verification results into a database'''''] and also [https://review.openstack.org/#/c/85584/ '''''a range of new commands to handle these results'''''], such as ''rally verify list'', ''rally verify detailed'' and others;
-* [https://review.openstack.org/#/c/84961/ '''''Validation for required parameters in benchmark scenarios'''''] has now been implemented through a new validator, added, as usual, as a decorator to the corresponding benchmark scenarios;
+This week, our work continues with such main novelties as adding support for [https://review.openstack.org/#/c/100579 Keystone API v3], adding context classes for [https://review.openstack.org/#/c/103306 avoiding vm creation if tenant has no network] and [https://review.openstack.org/#/c/104564 prepare an image that will have installed the required programs], mechanism to provide [https://review.openstack.org/#/c/103377 rally as a service], [https://review.openstack.org/#/c/104962 code refactoring in context manager] to make code more clear.
-This week, our work continues with several new '''''benchmark scenarios''''' (including those for [https://review.openstack.org/#/c/86337/ '''''Tempest''''']), new [https://review.openstack.org/#/c/86655/ '''''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.
@@ Line 297: / Line 292: @@
 Source code for Rally is hosted at GitHub: https://github.com/stackforge/rally<br/>
-You can track the overall progress in Rally via Stackalytics: http://stackalytics.com/?release=icehouse&metric=commits&project_type=all&module=rally <br/>
+You can track the overall progress in Rally via Stackalytics: http://stackalytics.com/?release=juno&metric=commits&project_type=all&module=rally <br/>
 Open reviews for Rally: https://review.openstack.org/#/q/status:open+rally,n,z
@@ Line 308: / Line 303: @@
+==== July 07, 2014 ====
+Hello stackers,
-==== April 7, 2014 ====
+here is the update for the last weeks. From all the work we've completed we would like to highlight the following:
-Hello stackers,
+* New benchmark scenarios:
+:* Benchmark to [https://review.openstack.org/#/c/89326 validate a '''keystone''' token N times at service endpoint] that allows to check effect of caching related to tokens;
+:* [https://review.openstack.org/#/c/93739 Scenario for benchmark '''Neutron''' ports].
+* [https://review.openstack.org/#/c/89555 Add nova floating ip management in VM scenario], before this patch the VM runcommand scenario used the fixed ip to ssh connect to the instance, this could only worked if fixed ip range was directly accessible with was the case in very limited deployments.
+* [https://review.openstack.org/#/c/95353 Add image context class] that allows adding images to each user for benchmarks, also this patch provides scenario which tests glance image-list command;
+* [https://review.openstack.org/#/c/99304 Large update of documentation] that simplifies its index structure and headings, extends the 'Benchmark' page with info from the "Main concepts" and adds some introductory text on Deploy & Verify parts;
+* [https://review.openstack.org/#/c/98158 Add service-level agreement checking] that allows to add section in task configuration that contains the criteria of success, e.g "less then 5% of failure rate", or "faster then 5 seconds for one iteration";
+* [https://review.openstack.org/#/c/103706 Use oslo.db module and remove rally/openstack/common/db].
-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:
-* [https://review.openstack.org/#/c/83835/ '''''Nova and Cinder quotas management'''''] through a new context class. Another example of how useful and easy to use contexts are in Rally;
-* '''''Concurrent users [https://review.openstack.org/#/c/79968/ creation] and [https://review.openstack.org/#/c/84106/ deletion]''''' in the user context. This change greatly reduces the runtime of this benchmarking step;
-* '''''New benchmark scenarios for [https://review.openstack.org/#/c/81781/ Keystone] and [https://review.openstack.org/#/c/82717/ Glance]''''';
-* Nice enhancement of the auto-generated report html page through adding [https://review.openstack.org/#/c/82912/ '''''histograms for runtimes'''''] there.
+Current work includes such interesting novelties as [https://blueprints.launchpad.net/rally/+spec/benchmark-context-semantic-validation context semantic validation], [https://review.openstack.org/#/c/102363 periodic runner refactoring], [https://review.openstack.org/#/c/102853 "rally info" command] which prints descriptions for different entities in Rally, [https://review.openstack.org/#/c/97556 checking if required services are available before starting the scenario] and refactoring of validation system, continue work on [https://review.openstack.org/94806 "stress" runner].
-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.
@@ Line 327: / Line 325: @@
 Source code for Rally is hosted at GitHub: https://github.com/stackforge/rally<br/>
-You can track the overall progress in Rally via Stackalytics: http://stackalytics.com/?release=icehouse&metric=commits&project_type=all&module=rally <br/>
+You can track the overall progress in Rally via Stackalytics: http://stackalytics.com/?release=juno&metric=commits&project_type=all&module=rally <br/>
 Open reviews for Rally: https://review.openstack.org/#/q/status:open+rally,n,z
@@ Line 340: / Line 338: @@
 ==== Archives ====
-* [[Rally/UpdatesMarch2014|Weekly updates archives - March 2014]]
+* [[Rally/UpdatesJune2014|Updates archives - June 2014]]
-* [[Rally/UpdatesFebruary2014|Weekly updates archives - February 2014]]
+* [[Rally/UpdatesMay2014|Updates archives - May 2014]]
-* [[Rally/UpdatesJanuary2014|Weekly updates archives - January 2014]]
+* [[Rally/UpdatesApril2014|Updates archives - April 2014]]
-* [[Rally/UpdatesDecember2013|Weekly updates archives - December 2013]]
+* [[Rally/UpdatesMarch2014|Updates archives - March 2014]]
-* [[Rally/UpdatesNovember2013|Weekly updates archives - November 2013]]
+* [[Rally/UpdatesFebruary2014|Updates archives - February 2014]]
+* [[Rally/UpdatesJanuary2014|Updates archives - January 2014]]
+* [[Rally/UpdatesDecember2013|Updates archives - December 2013]]
+* [[Rally/UpdatesNovember2013|Updates archives - November 2013]]