<div dir="ltr">Jay, <div><br></div><div><br></div><div><span style="font-family:arial,sans-serif;font-size:13px">Or, alternately, just have Rally as part of Tempest.</span><br style="font-family:arial,sans-serif;font-size:13px">
</div><div><span style="font-family:arial,sans-serif;font-size:13px"><br></span></div><div><span style="font-family:arial,sans-serif;font-size:13px"><br></span></div><div><span style="font-family:arial,sans-serif">Actually, tempest is used only to verify that cloud works properly.</span></div>
<div><span style="font-family:arial,sans-serif">And verification is only small part of the Rally.</span><br></div><div><span style="font-family:arial,sans-serif"><br></span></div><div><span style="font-family:arial,sans-serif">At this moment we are using fuel-ostf-tests, but we are going to use tempest to verify cloud. </span><br>
</div><div><span style="font-family:arial,sans-serif"><br></span></div><div><span style="font-family:arial,sans-serif"><br></span></div><div><br></div><div>Best regards,</div><div>Boris Pavlovic</div><div>---</div><div>Mirantis Inc. </div>
<div><span style="font-family:arial,sans-serif;font-size:13px"><br></span></div><div><span style="font-family:arial,sans-serif;font-size:13px"><br>
</span></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Oct 17, 2013 at 10:31 PM, Jay Pipes <span dir="ltr"><<a href="mailto:jaypipes@gmail.com" target="_blank">jaypipes@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On 10/17/2013 02:22 PM, Joshua Harlow wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Great work boris (and others)!<br>
<br>
I know at yahoo! me and others are very happy there is a community<br>
driven project to gather this kind of information in a repeatable and<br>
publicized manner.<br>
<br>
It has been something that has been missing from the development process<br>
(an easy way to how code that is changed affects the overall systems<br>
performance).<br>
<br>
This type of project will help make that much more visible, and allow a<br>
greater focus on the problematic areas (the scheduler I know is one).<br>
<br>
Very good news, looking forward to getting y! involved as much as I can.<br>
<br>
-Josh<br>
<br>
PS: not sure if we should change the name, I know there is an agile<br>
planning company @ <a href="http://www.rallydev.com" target="_blank">http://www.rallydev.com</a> named rally software. Yahoo!<br>
uses it so that’s how I know the name.<br>
<br>
Might just be a good idea to check the trademarks and such beforehand,<br>
to avoid a change at a later stage.<br>
</blockquote>
<br></div>
Or, alternately, just have Rally as part of Tempest.<br>
<br>
-jay<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
From: Boris Pavlovic <<a href="mailto:bpavlovic@mirantis.com" target="_blank">bpavlovic@mirantis.com</a><br>
<mailto:<a href="mailto:bpavlovic@mirantis.com" target="_blank">bpavlovic@mirantis.com</a><u></u>>><div class="im"><br>
Reply-To: OpenStack Development Mailing List<br>
<<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.<u></u>openstack.org</a><br></div>
<mailto:<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.<u></u>openstack.org</a>>><div class="im"><br>
Date: Wednesday, October 16, 2013 3:41 PM<br>
To: OpenStack Development Mailing List<br>
<<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.<u></u>openstack.org</a><br></div>
<mailto:<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.<u></u>openstack.org</a>>><div><div class="h5"><br>
Subject: [openstack-dev] Announce of Rally - benchmarking system for<br>
OpenStack<br>
<br>
Hi Stackers,<br>
<br>
<br>
We are thrilled to present to you Rally, the benchmarking system for<br>
OpenStack.<br>
<br>
<br>
It is not a secret that we have performance & scaling issues and that<br>
OpenStack won’t scale out of box. It is also well known that if you get<br>
your super big DC (5k-15k servers) you are able to find & fix all<br>
OpenStack issues in few months (like Rackspace, BlueHost & others have<br>
proved). So the problem with performance at scale is solvable.<br>
<br>
<br>
The main blocker to fix such issues in community is that there is no<br>
simple way to get relevant and repeatable “numbers” that represent<br>
OpenStack performance at scale. It is not enough to tune an individual<br>
OpenStack component, because its performance at scale is no guarantee<br>
that it will not introduce a bottleneck somewhere else.<br>
<br>
<br>
The correct approach to comprehensively test OpenStack scalability, in<br>
our opinion, consists of the following four steps:<br>
<br>
1) Deploy OpenStack<br>
2) Create load by simultaneously making OpenStack API calls<br>
3) Collect performance and profile data<br>
4) Make data easy to consume by presenting it in a humanly readable form<br>
<br>
<br>
Rally is the system that implements all the steps above plus it<br>
maintains an extendable repository of standard performance tests. To use<br>
Rally, a user has to specify where to deploy OS, select the deployment<br>
mechanism (DevStack, Triple-O, Fuel, Etc.) and the set of benchmarking<br>
tests to run.<br>
<br>
For more details and how to use it take a look at our wiki<br>
<a href="https://wiki.openstack.org/wiki/Rally" target="_blank">https://wiki.openstack.org/<u></u>wiki/Rally</a> it should already work out of box.<br>
<br>
<br>
Happy hunting!<br>
<br>
<br>
Links:<br>
<br>
1. Code: <a href="https://github.com/stackforge/rally" target="_blank">https://github.com/stackforge/<u></u>rally</a><br>
<br>
2. Wiki: <a href="https://wiki.openstack.org/wiki/Rally" target="_blank">https://wiki.openstack.org/<u></u>wiki/Rally</a><br>
<br>
2. Launchpad: <a href="https://launchpad.net/rally" target="_blank">https://launchpad.net/rally</a><br>
<br>
3. Statistics:<br>
<a href="http://stackalytics.com/?release=havana&project_type=All&module=rally" target="_blank">http://stackalytics.com/?<u></u>release=havana&project_type=<u></u>All&module=rally</a><br>
<br>
4. RoadMap: <a href="https://wiki.openstack.org/wiki/Rally/RoadMap" target="_blank">https://wiki.openstack.org/<u></u>wiki/Rally/RoadMap</a><br>
<br>
<br>
Best regards,<br>
Boris Pavlovic<br>
---<br>
Mirantis Inc.<br>
<br>
<br></div></div>
______________________________<u></u>_________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.<u></u>org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/<u></u>cgi-bin/mailman/listinfo/<u></u>openstack-dev</a><br>
<br>
</blockquote>
<br>
<br>
______________________________<u></u>_________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.<u></u>org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/<u></u>cgi-bin/mailman/listinfo/<u></u>openstack-dev</a><br>
</blockquote></div><br></div>