<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px;">
+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. </div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px;">
<div>
<div>-- </div>
<div>Regards,</div>
</div>
<div>Marco</div>
</div>
</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px;">
<br>
</div>
<span id="OLK_SRC_BODY_SECTION" style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px;">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>Boris Pavlovic <<a href="mailto:boris@pavlovic.me">boris@pavlovic.me</a>><br>
<span style="font-weight:bold">Reply-To: </span>"OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
<span style="font-weight:bold">Date: </span>Monday, July 21, 2014 at 2:53 PM<br>
<span style="font-weight:bold">To: </span>OpenStack Development Mailing List <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>>, "<a href="mailto:openstack-tc@lists.openstack.org">openstack-tc@lists.openstack.org</a>"
<<a href="mailto:openstack-tc@lists.openstack.org">openstack-tc@lists.openstack.org</a>><br>
<span style="font-weight:bold">Subject: </span>[openstack-dev] [tc][rally] Application for a new OpenStack Program: Performance and Scalability<br>
</div>
<div><br>
</div>
<div>
<div>
<div dir="ltr">Hi Stackers and TC,<br>
<br>
The Rally contributor team would like to propose a new OpenStack program<br>
with a mission to provide scalability and performance benchmarking, and<br>
code profiling tools for OpenStack components.<br>
<br>
We feel we've achieved a critical mass in the Rally project, with an<br>
active, diverse contributor team. The Rally project will be the initial<br>
project in a new proposed "Performance and Scalability" program.<br>
<br>
Below, the details on our proposed new program.<br>
<br>
Thanks for your consideration,<br>
Boris
<div><br>
</div>
<div><br>
<br>
[1] <a href="https://review.openstack.org/#/c/108502/">https://review.openstack.org/#/c/108502/</a>
<div><br>
<div>
<div><br>
</div>
<div>Official Name<br>
=============<br>
<br>
Performance and Scalability<br>
<br>
Codename<br>
========<br>
<br>
Rally<br>
<br>
Scope<br>
=====<br>
<br>
Scalability benchmarking, performance analysis, and profiling of<br>
OpenStack components and workloads<br>
<br>
Mission<br>
=======<br>
<br>
To increase the scalability and performance of OpenStack clouds by:<br>
<br>
* defining standard benchmarks<br>
* sharing performance data between operators and developers<br>
* providing transparency of code paths through profiling tools<br>
<br>
Maturity<br>
========<br>
<br>
* Meeting logs <a href="http://eavesdrop.openstack.org/meetings/rally/2014/">http://eavesdrop.openstack.org/meetings/rally/2014/</a><br>
* IRC channel: #openstack-rally<br>
* Rally performance jobs are in (Cinder, Glance, Keystone & Neutron)<br>
check pipelines.<br>
* > 950 commits over last 10 months<br>
* Large, diverse contributor community<br>
* <a href="http://stackalytics.com/?release=juno&metric=commits&project_type=All&module=rally">http://stackalytics.com/?release=juno&metric=commits&project_type=All&module=rally</a></div>
<div> * <a href="http://stackalytics.com/report/contribution/rally/180">http://stackalytics.com/report/contribution/rally/180</a><br>
<br>
* Non official lead of project is Boris Pavlovic<br>
* Official election In progress.<br>
<br>
Deliverables<br>
============<br>
<br>
Critical deliverables in the Juno cycle are:<br>
<br>
* extending Rally Benchmark framework to cover all use cases that are<br>
required by all OpenStack projects<br>
* integrating OSprofiler in all core projects<br>
* increasing functional & unit testing coverage of Rally.<br>
<br>
Discussion<br>
==========<br>
<br>
One of the major goals of Rally is to make it simple to share results of<br>
standardized benchmarks and experiments between operators and<br>
developers. When an operator needs to verify certain performance<br>
indicators meet some service level agreement, he will be able to run<br>
benchmarks (from Rally) and share with the developer community the<br>
results along with his OpenStack configuration. These benchmark results<br>
will assist developers in diagnosing particular performance and<br>
scalability problems experienced with the operator's configuration.<br>
<br>
Another interesting area is Rally & the OpenStack CI process. Currently,<br>
working on performance issues upstream tends to be a more social than<br>
technical process. We can use Rally in the upstream gates to identify<br>
performance regressions and measure improvement in scalability over<br>
time. The use of Rally in the upstream gates will allow a more rigorous,<br>
scientific approach to performance analysis. In the case of an<br>
integrated OSprofiler, it will be possible to get detailed information<br>
about API call flows (e.g. duration of API calls in different services).</div>
</div>
</div>
<div><br>
</div>
<div><br>
</div>
</div>
</div>
</div>
</div>
</span>
</body>
</html>