<html><body><p>I couldn't have said it better, Sean.<br><br>Ryan Moats<br><br><tt>"Sean M. Collins" <sean@coreitpro.com> wrote on 09/14/2015 05:01:03 PM:<br><br>> From: "Sean M. Collins" <sean@coreitpro.com></tt><br><tt>> To: "OpenStack Development Mailing List (not for usage questions)" <br>> <openstack-dev@lists.openstack.org></tt><br><tt>> Date: 09/14/2015 05:01 PM</tt><br><tt>> Subject: [openstack-dev] [neutron][L3][QA] DVR job failure rate and <br>> maintainability</tt><br><tt>> <br>> [adding neutron tag to subject and resending]<br>> <br>> Hi,<br>> <br>> Carl Baldwin, Doug Wiegley, Matt Kassawara, Ryan Moats, and myself are<br>> at the QA sprint in Fort Collins. Earlier today there was a discussion<br>> about the failure rate about the DVR job, and the possible impact that<br>> it is having on the gate.<br>> <br>> Ryan has a good patch up that shows the failure rates over time:<br>> <br>> <a href="https://review.openstack.org/223201">https://review.openstack.org/223201</a><br>> <br>> To view the graphs, you go over into your neutron git repo, and open the<br>> .html files that are present in doc/dashboards - which should open up<br>> your browser and display the Graphite query.<br>> <br>> Doug put up a patch to change the DVR job to be non-voting while we<br>> determine the cause of the recent spikes:<br>> <br>> <a href="https://review.openstack.org/223173">https://review.openstack.org/223173</a><br>> <br>> There was a good discussion after pushing the patch, revolving around<br>> the need for Neutron to have DVR, to fit operational and reliability<br>> requirements, and help transition away from Nova-Network by providing<br>> one of many solutions similar to Nova's multihost feature. I'm skipping<br>> over a huge amount of context about the Nova-Network and Neutron work,<br>> since that is a big and ongoing effort. <br>> <br>> DVR is an important feature to have, and we need to ensure that the job<br>> that tests DVR has a high pass rate.<br>> <br>> One thing that I think we need, is to form a group of contributors that<br>> can help with the DVR feature in the immediate term to fix the current<br>> bugs, and longer term maintain the feature. It's a big task and I don't<br>> believe that a single person or company can or should do it by themselves.<br>> <br>> The L3 group is a good place to start, but I think that even within the<br>> L3 team we need dedicated and diverse group of people who are interested<br>> in maintaining the DVR feature. <br>> <br>> Without this, I think the DVR feature will start to bit-rot and that<br>> will have a significant impact on our ability to recommend Neutron as a<br>> replacement for Nova-Network in the future.<br>> <br>> -- <br>> Sean M. Collins<br>> <br>> __________________________________________________________________________<br>> OpenStack Development Mailing List (not for usage questions)<br>> Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe<br>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>> <br>> __________________________________________________________________________<br>> OpenStack Development Mailing List (not for usage questions)<br>> Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe<br>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>> <br></tt><BR>
</body></html>