Open Stack

Great work boris (and others)!

I know at yahoo! me and others are very happy there is a community driven project to gather this kind of information in a repeatable and publicized manner.

It has been something that has been missing from the development process (an easy way to how code that is changed affects the overall systems performance).

This type of project will help make that much more visible, and allow a greater focus on the problematic areas (the scheduler I know is one).

Very good news, looking forward to getting y! involved as much as I can.

-Josh

PS: not sure if we should change the name, I know there is an agile planning company @ http://www.rallydev.com named rally software. Yahoo! uses it so that’s how I know the name.

Might just be a good idea to check the trademarks and such beforehand, to avoid a change at a later stage.

From: Boris Pavlovic <bpavlovic at mirantis.com<mailto:bpavlovic at mirantis.com>>
Reply-To: OpenStack Development Mailing List <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Date: Wednesday, October 16, 2013 3:41 PM
To: OpenStack Development Mailing List <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Subject: [openstack-dev] Announce of Rally - benchmarking system for OpenStack

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!


Links:

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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20131017/f84abe82/attachment.html>