
<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;" class="">+1<div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Jul 21, 2016, at 5:13 PM, Kevin Benton <<a href="mailto:kevin@benton.pub" class="">kevin@benton.pub</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">+1</div><div class="gmail_extra"><br class=""><div class="gmail_quote">On Thu, Jul 21, 2016 at 2:41 PM, Carl Baldwin <span dir="ltr" class=""><<a href="mailto:carl@ecbaldwin.net" target="_blank" class="">carl@ecbaldwin.net</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr" class="">+1 from me</div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br class=""><div class="gmail_quote">On Thu, Jul 21, 2016 at 1:35 PM, Assaf Muller <span dir="ltr" class=""><<a href="mailto:assaf@redhat.com" target="_blank" class="">assaf@redhat.com</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">As Neutron's so called testing lieutenant I would like to propose<br class="">

Jakub Libosvar to be a core in the testing area.<br class="">

<br class="">

Jakub has demonstrated his inherent interest in the testing area over<br class="">

the last few years, his reviews are consistently insightful and his<br class="">

numbers [1] are in line with others and I know will improve if given<br class="">

the responsibilities of a core reviewer. Jakub is deeply involved with<br class="">

the project's testing infrastructures and CI systems.<br class="">

<br class="">

As a reminder the expectation from cores is found here [2], and<br class="">

specifically for cores interesting in helping out shaping Neutron's<br class="">

testing story:<br class="">

<br class="">

* Guide community members to craft a testing strategy for features [3]<br class="">

* Ensure Neutron's testing infrastructures are sufficiently<br class="">

sophisticated to achieve the above.<br class="">

* Provide leadership when determining testing Do's & Don'ts [4]. What<br class="">

makes for an effective test?<br class="">

* Ensure the gate stays consistently green<br class="">

<br class="">

And more tactically we're looking at finishing the Tempest/Neutron<br class="">

tests dedup [5] and to provide visual graphing for historical control<br class="">

and data plane performance results similar to [6].<br class="">

<br class="">

[1] <a href="http://stackalytics.com/report/contribution/neutron/90" rel="noreferrer" target="_blank" class="">http://stackalytics.com/report/contribution/neutron/90</a><br class="">

[2] <a href="http://docs.openstack.org/developer/neutron/policies/neutron-teams.html" rel="noreferrer" target="_blank" class="">http://docs.openstack.org/developer/neutron/policies/neutron-teams.html</a><br class="">

[3] <a href="http://docs.openstack.org/developer/neutron/devref/development.environment.html#testing-neutron" rel="noreferrer" target="_blank" class="">http://docs.openstack.org/developer/neutron/devref/development.environment.html#testing-neutron</a><br class="">

[4] <a href="https://assafmuller.com/2015/05/17/testing-lightning-talk/" rel="noreferrer" target="_blank" class="">https://assafmuller.com/2015/05/17/testing-lightning-talk/</a><br class="">

[5] <a href="https://etherpad.openstack.org/p/neutron-tempest-defork" rel="noreferrer" target="_blank" class="">https://etherpad.openstack.org/p/neutron-tempest-defork</a><br class="">

[6] <a href="https://www.youtube.com/watch?v=a0qlsH1hoKs&feature=youtu.be&t=24m22s" rel="noreferrer" target="_blank" class="">https://www.youtube.com/watch?v=a0qlsH1hoKs&feature=youtu.be&t=24m22s</a><br class="">

<br class="">

__________________________________________________________________________<br class="">

OpenStack Development Mailing List (not for usage questions)<br class="">

Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe" rel="noreferrer" target="_blank" class="">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br class="">

<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class="">

</blockquote></div><br class=""></div>

</div></div><br class="">__________________________________________________________________________<br class="">

OpenStack Development Mailing List (not for usage questions)<br class="">

Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe" rel="noreferrer" target="_blank" class="">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br class="">

<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class="">

<br class=""></blockquote></div><br class=""></div>

__________________________________________________________________________<br class="">OpenStack Development Mailing List (not for usage questions)<br class="">Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org" class="">OpenStack-dev-request@lists.openstack.org</a>?subject:unsubscribe<br class=""><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class=""></div></blockquote></div><br class=""></div></body></html>