Open Stack

+1 At yahoo we are using and contributing to Rally.  Within our company performance engineering and QE are distinct job groups with different skill sets and focus.  As a result, I think that it makes perfect sense to have a dedicated program for performance and scalability within OpenStack.  I also think it makes sense to start growing that capability from active community of developers already working on Rally and OSprofiler.
--
Regards,
Marco

From: Boris Pavlovic <boris at pavlovic.me<mailto:boris at pavlovic.me>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Date: Monday, July 21, 2014 at 2:53 PM
To: OpenStack Development Mailing List <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>, "openstack-tc at lists.openstack.org<mailto:openstack-tc at lists.openstack.org>" <openstack-tc at lists.openstack.org<mailto:openstack-tc at lists.openstack.org>>
Subject: [openstack-dev] [tc][rally] Application for a new OpenStack Program: Performance and Scalability

Hi Stackers and TC,

The Rally contributor team would like to propose a new OpenStack program
with a mission to provide scalability and performance benchmarking, and
code profiling tools for OpenStack components.

We feel we've achieved a critical mass in the Rally project, with an
active, diverse contributor team. The Rally project will be the initial
project in a new proposed "Performance and Scalability" program.

Below, the details on our proposed new program.

Thanks for your consideration,
Boris



[1] https://review.openstack.org/#/c/108502/


Official Name
=============

Performance and Scalability

Codename
========

Rally

Scope
=====

Scalability benchmarking, performance analysis, and profiling of
OpenStack components and workloads

Mission
=======

To increase the scalability and performance of OpenStack clouds by:

* defining standard benchmarks
* sharing performance data between operators and developers
* providing transparency of code paths through profiling tools

Maturity
========

* Meeting logs http://eavesdrop.openstack.org/meetings/rally/2014/
* IRC channel: #openstack-rally
* Rally performance jobs are in (Cinder, Glance, Keystone & Neutron)
check pipelines.
* > 950 commits over last 10 months
* Large, diverse contributor community
 * http://stackalytics.com/?release=juno&metric=commits&project_type=All&module=rally
 * http://stackalytics.com/report/contribution/rally/180

* Non official lead of project is Boris Pavlovic
 * Official election In progress.

Deliverables
============

Critical deliverables in the Juno cycle are:

* extending Rally Benchmark framework to cover all use cases that are
required by all OpenStack projects
* integrating OSprofiler in all core projects
* increasing functional & unit testing coverage of Rally.

Discussion
==========

One of the major goals of Rally is to make it simple to share results of
standardized benchmarks and experiments between operators and
developers. When an operator needs to verify certain performance
indicators meet some service level agreement, he will be able to run
benchmarks (from Rally) and share with the developer community the
results along with his OpenStack configuration. These benchmark results
will assist developers in diagnosing particular performance and
scalability problems experienced with the operator's configuration.

Another interesting area is Rally & the OpenStack CI process. Currently,
working on performance issues upstream tends to be a more social than
technical process. We can use Rally in the upstream gates to identify
performance regressions and measure improvement in scalability over
time. The use of Rally in the upstream gates will allow a more rigorous,
scientific approach to performance analysis. In the case of an
integrated OSprofiler, it will be possible to get detailed information
about API call flows (e.g. duration of API calls in different services).


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140722/9a557b41/attachment.html>