[openstack-dev] Announce of Rally - benchmarking system for OpenStack

Tim Bell Tim.Bell at cern.ch
Sat Dec 28 19:40:08 UTC 2013

I think there also needs to be a scalability best practise and reference architecture.

Benchmarking allows us to identify problems with the code but we also need some community wisdom on how to deploy at scale.

Does this fit within Rally or can you advise where this community wisdom should be accumulated ?


From: Ali Gamal [mailto:agamal at itsyn.com]
Sent: 28 December 2013 20:31
To: OpenStack Development Mailing List
Cc: Ali Beddah
Subject: Re: [openstack-dev] Announce of Rally - benchmarking system for OpenStack

On Oct 17, 2013 12:45 AM, "Boris Pavlovic" <bpavlovic at mirantis.com<mailto:bpavlovic at mirantis.com>> wrote:
Hi Stackers,

We are thrilled to present to you Rally, the benchmarking system for OpenStack.

It is not a secret that we have performance & scaling issues and that OpenStack won't scale out of box. It is also well known that if you get your super big DC (5k-15k servers) you are able to find & fix all OpenStack issues in few months (like Rackspace, BlueHost & others have proved). So the problem with performance at scale is solvable.

The main blocker to fix such issues in community is that there is no simple way to get relevant and repeatable "numbers" that represent OpenStack performance at scale. It is not enough to tune an individual OpenStack component, because its performance at scale is no guarantee that it will not introduce a bottleneck somewhere else.

The correct approach to comprehensively test OpenStack scalability, in our opinion, consists of the following four steps:

1)  Deploy OpenStack
2)  Create load by simultaneously making OpenStack API calls
3)  Collect performance and profile data
4)  Make data easy to consume by presenting it in a humanly readable form

Rally is the system that implements all the steps above plus it maintains an extendable repository of standard performance tests. To use Rally, a user has to specify where to deploy OS, select the deployment mechanism (DevStack, Triple-O, Fuel, Etc.) and the set of benchmarking tests to run.

For more details and how to use it take a look at our wiki https://wiki.openstack.org/wiki/Rally it should already work out of box.

Happy hunting!


1. Code: https://github.com/stackforge/rally

2. Wiki: https://wiki.openstack.org/wiki/Rally
2. Launchpad: https://launchpad.net/rally
3. Statistics: http://stackalytics.com/?release=havana&project_type=All&module=rally
4. RoadMap: https://wiki.openstack.org/wiki/Rally/RoadMap

Best regards,
Boris Pavlovic
Mirantis Inc.

OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org<mailto:OpenStack-dev at lists.openstack.org>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20131228/1fb08064/attachment.html>

More information about the OpenStack-dev mailing list