Difference between revisions of "Rally"
(→Rally in action)
(→Performance of Nova instance list command)
|Line 81:||Line 81:|
=== Performance of Nova instance list command ===
=== Performance of Nova instance list command ===
iteration and VM list
== How To ==
== How To ==
Revision as of 16:33, 23 March 2014
- 1 What is Rally?
- 2 Use Cases
- 3 Architecture
- 4 Rally in action
- 5 How To
- 6 Weekly updates
- 7 Rally in the World
- 8 Join Rally team
What is Rally?
If you are here, you are probably familiar with OpenStack and you also know that it's a really huge ecosystem of cooperative services. When something fails, performs slowly or doesn't scale, it's really hard to answer different questions on "what", "why" and "where" has happened. Another reason why you could be here is that you would like to build an OpenStack CI/CD system that will allow you to improve SLA, performance and stability of OpenStack continuously.
The OpenStack QA team mostly works on CI/CD that ensures that new patches don't break some specific single node installation of OpenStack. On the other hand it's clear that such CI/CD is only an indication and does not cover all cases (e.g. if a cloud works well on a single node installation it doesn't mean that it will continue to do so on a 1k servers installation under high load as well). Rally aims to fix this and help us to answer the question "How does OpenStack work at scale?". To make it possible, we are going to automate and unify all steps that are required for benchmarking OpenStack at scale: multi-node OS deployment, verification, benchmarking & profiling.
- Deploy engine is not yet another deployer of OpenStack, but just a pluggable mechanism that allows to unify & simplify work with different deployers like: DevStack, Fuel, Anvil on hardware/VMs that you have.
- Verification - (work in progress) uses tempest to verify the functionality of a deployed OpenStack cloud. In future Rally will support other OS verifiers.
- Benchmark engine - allows to create parameterized load on the cloud based on a big repository of benchmarks.
For more information about how it works take a look at Rally Architecture
Before diving deep in Rally architecture let's take a look at 3 major high level Rally Use Cases:
Typical cases where Rally aims to help are:
- Automate measuring & profiling focused on how new code changes affect the OS performance;
- Using Rally profiler to detect scaling & performance issues;
- Investigate how different deployments affect the OS performance:
- Find the set of suitable OpenStack deployment architectures;
- Create deployment specifications for different loads (amount of controllers, swift nodes, etc.);
- Automate the search for hardware best suited for particular OpenStack cloud;
- Automate the production cloud specification generation:
- Determine terminal loads for basic cloud operations: VM start & stop, Block Device create/destroy & various OpenStack API methods;
- Check performance of basic cloud operations in case of different loads.
Usually OpenStack projects are as-a-Service, so Rally provides this approach and a CLI driven approach that does not require a daemon:
- Rally as-a-Service: Run rally as a set of daemons that present Web UI (work in progress) so 1 RaaS could be used by whole team.
- Rally as-an-App: Rally as a just lightweight CLI app (without any daemons), that makes it simple to develop & much more portable.
How is this possible? Take a look at diagram below:
So what is behind Rally?
Rally consists of 4 main components:
- Server Providers - provide servers (virtual servers), with ssh access, in one L3 network.
- Deploy Engines - deploy OpenStack cloud on servers that are presented by Server Providers
- Verification - component that runs tempest (or another pecific set of tests) against a deployed cloud, collects results & presents them in human readable form.
- Benchmark engine - allows to write parameterized benchmark scenarios & run them against the cloud.
But why does Rally need these components?
It becomes really clear if we try to imagine: how I will benchmark cloud at Scale, if ...
Rally in action
How amqp_rpc_single_reply_queue affects performance
To show Rally's capabilities and potential we used NovaServers.boot_and_destroy scenario to see how amqp_rpc_single_reply_queue option affects VM bootup time. Some time ago it was shown that cloud performance can be boosted by setting it on so naturally we decided to check this result. To make this test we issued requests for booting up and deleting VMs for different number of concurrent users ranging from one to 30 with and without this option set. For each group of users a total number of 200 requests was issued. Averaged time per request is shown below:
So apparently this option affects cloud performance, but not in the way it was thought before.
Performance of Nova instance list command
Context: 1 OpenStack user
Scenario: 1) boot VM from this user 2) list VM
Runner: Repeat 200 times.
As a result, every next iteration user has more and more VMs and perfromance of VM list is degrading quite fast:
Actually there are only 3 steps that should be interesting for you:
Each week we write up on a special weekly updates page what sort of things have been accomplished in Rally during the past week and what are our plans for the next one. Below you can find the most recent report.
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:
- An enormously important and overall refactoring patch that brings different optimizations to the config validation step, to the CLI output/logging and also (NB!) changes the input task configuration file format (take a look at the updated task configuration samples);
- An important step on the way to a complete Rally-Tempest integration is adding the ability to launch Tempest tests without "sudo";
- OpenStack clients helper module refactoring, which is concentrated on reimplementing the "lazy" client handles in a more elegant way and also making them accessible in a direct way, without auxiliary methods like rally.benchmark.utils.create_openstack_clients(), which made the code unreasonably more complicated;
- We've also added several missing unit tests: the ones for the "deployment list" command as well as for the Authenticate benchmark scenario group.
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
The Rally team
Rally in the World
||Benchmark as a Service OpenStack-Rally||OpenStack Meetup Bangalore|
||Benchmarking OpenStack With Rally||http://www.thegeekyway.com/|
||Benchmarking OpenStack at megascale: How we tested Mirantis OpenStack at SoftLayer||http://www.mirantis.com/blog/|
||Benchmark OpenStack at Scale||Openstack summit Hong Kong|
Join Rally team
Open and assigned tasks
To get account ping Boris in IRC (boris-42) or email me (boris(at)pavlovic.me)
The Rally project team holds weekly meetings on Tuesdays at 1700 UTC in IRC, at the