<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On 23 April 2015 at 09:14, Chris Dent <span dir="ltr"><<a href="mailto:chdent@redhat.com" target="_blank">chdent@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><br>
This might be a bit presumptuous, but why not give it a try...<br>
<br>
This cycle's TC elections didn't come with a set of prepackaged<br>
questions and though the self-nomination messages have included some<br>
very interesting stuff I think it would be useful to get answers<br>
from the candidates on at least one topical but open-ended<br>
question. Maybe other people have additional questions they think<br>
are important but this one is the one that matters to me and also<br>
captures the role that I wish the TC filled more strongly. Here's<br>
the preamble:<br>
<br>
There are lots of different ways to categorize the various<br>
stakeholders in the OpenStack community, no list is complete. For<br>
the sake of this question the people I'm concerned with are the<br>
developers, end-users and operators of OpenStack: the individuals<br>
who are actively involved with it on a daily basis. I'm intentionally<br>
leaving out things like "the downstream".<br>
<br>
There are many different ways to define "quality". For the sake of<br>
this question feel free to use whatever definition you like but take<br>
it as given that "quality" needs to be improved.<br>
<br>
Here's the question:<br>
<br>
What can and should the TC at large, and you specifically, do to ensure<br>
quality improves for the developers, end-users and operators of<br>
OpenStack as a full system, both as a project being developed and a<br>
product being used?</blockquote><div><br></div>I am possibly the latest candidate to respond to this thread...what a lousy candidate that I am! :)<div><br></div><div>Without incurring the risk of becoming incredibly verbose, and trying to keep this discussion down to earth, one thing I would like to see happen is addressing the sort of quality that can be qualitatively measured on an ongoing basis. For instance, to date we cannot tell at any given time (and without support of downstream tools) whether certain key operations (like VM boot) have degraded because of a specific change (if there is, as a developer I'd be keen to learn how to take advantage of it, but that's another discussion)!</div><div><br></div><div>For instance, when I was at VMware and in charge of 3rd party CI, I designed a small mechanism to track the mobile average of test run times that would tell a developer the impact of his/her change to the overall performance of the system (single devstack). For instance, in change [1], the VMware CI reported back <font color="#000000" face="sans-serif">94.32% faster than the average run time. That clearly meant that the change had no negative impact to the operations that involved the VMware plugin for Neutron. Had that number been 150%, that would have alerted a reviewer and triggered further analysis.</font></div><div><br></div><div><font color="#000000" face="sans-serif">That number is obviously a coarse grained way of capturing quality, and may have its own flaws but I found it incredibly useful and I would like to see something along those lines be implemented in Zuul.</font></div><div><font color="#000000" face="sans-serif"><br></font></div><div><div><font color="#000000" face="sans-serif">Anyhow, I hope you get the gist, should you want to know more, I guess you'd have to vote for me :P</font></div></div><div><font color="#000000" face="sans-serif"><br></font></div><div><font color="#000000" face="sans-serif">Cheers,</font></div><div><font color="#000000" face="sans-serif">Armando</font></div><div><br></div><div>[1] <a href="https://review.openstack.org/#/c/80387/" target="_blank">https://review.openstack.org/#/c/80387/</a></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><span><font color="#888888"><br>
<br>
-- <br>
Chris Dent tw:@anticdent freenode:cdent<br>
<a href="https://tank.peermore.com/tanks/cdent" target="_blank">https://tank.peermore.com/tanks/cdent</a><br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</font></span></blockquote></div><br></div></div>