<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>
<div>Since Rally is the first OpenStack project that I contributed to, I can personally vouch for Boris' magical abilities to welcome new contributors and set the technical direction for the project. If you spend some time in the #openstack-rally irc you quickly
realize that boris-42 is available across multiple timezones to answer questions, delegate bugs and features, and provide a vision for what Rally should be.</div>
<div>
<div>
<div>-- </div>
<div>Regards,</div>
</div>
<div>Marco</div>
</div>
</div>
</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<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:bpavlovic@mirantis.com">bpavlovic@mirantis.com</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 11:38 AM<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>><br>
<span style="font-weight:bold">Subject: </span>[openstack-dev] [Rally] PTL Candidacy<br>
</div>
<div><br>
</div>
<div>
<div>
<div dir="ltr">Hi,
<div><br>
</div>
<div>I would like to propose my candidacy for Rally PTL.</div>
<div><br>
</div>
<div>I started this project to make benchmarking of OpenStack simple as possible. This means not only load generation, but as well OpenStack specific benchmark framework, data analyze and integration with gates. All these things should make it simple for developers
and operators to benchmark (perf, scale, stress test) OpenStack, share experiments & results, and have a fast way to find what produce bottleneck or just to ensure that OpenStack works well under load that they are expecting. </div>
<div><br>
</div>
<div>I am current non official PTL and in my responsibilities are such things like:</div>
<div>1) Adoption of Rally architecture to cover everybody's use cases</div>
<div>2) Building & managing work of community</div>
<div>3) Writing a lot of code</div>
<div>4) Working on docs & wiki </div>
<div>5) Helping newbies to join Rally team </div>
<div><br>
</div>
<div>As a PTL I would like to continue work and finish my initial goal:</div>
<div>1) Ensure that everybody's use cases are fully covered</div>
<div>2) There is no monopoly in project</div>
<div>3) Run Rally in gates of all OpenStack projects (currently we have check jobs in Keystone, Cinder, Glance & Neutron)</div>
<div>4) Continue work on making project more mature. It covers such topics like increasing unit and functional test coverage and making Rally absolutely safe to run against any production cloud)</div>
<div><br>
</div>
<div><br>
</div>
<div>Best regards,</div>
<div>Boris Pavlovic</div>
</div>
</div>
</div>
</span>
</body>
</html>