<div dir="ltr">Thanks Sean, comments inline.<br><div class="gmail_extra"><br><div class="gmail_quote">On 6 July 2015 at 16:58, Sean M. Collins <span dir="ltr"><<a href="mailto:sean@coreitpro.com" target="_blank">sean@coreitpro.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">I'd also like to chime in - we've had some discussions on -infra today<br>
about the partial upgrade issue, and collected the following notes on an<br>
etherpad.<br>
<br>
<a href="https://etherpad.openstack.org/p/neutron-partial-upgrades" rel="noreferrer" target="_blank">https://etherpad.openstack.org/p/neutron-partial-upgrades</a><br>
<br>
One of the things identified, was the complexity of the DVR feature in<br>
Neutron, and an attempt to simplify the partial upgrade job by not<br>
enabling the DVR feature.<br></blockquote><div><br></div><div>The DVR issue is entirely orthogonal to this, but I am willing to play along.</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">
<br>
<a href="http://eavesdrop.openstack.org/meetings/networking/2015/networking.2015-07-06-21.00.log.html" rel="noreferrer" target="_blank">http://eavesdrop.openstack.org/meetings/networking/2015/networking.2015-07-06-21.00.log.html</a><br>
<br>
Clark Boylan has proposed a patch to create a new job that runs on<br>
multiple nodes, but does not have DVR enabled, in the hopes that having<br>
less moving parts will allow the multinode grenade work to continue on a<br>
parallel track, </blockquote><div><br></div><div>Who is leading the Grenade effort? Is it Clark?</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">with bugfixes or additional work on the Neutron DVR<br>
feature not blocking the overall effort. The idea would be eventually to<br>
enable DVR, once we have taken care of all the other work that needs to<br>
be done.<br>
<br>
<a href="https://review.openstack.org/#/c/198906/" rel="noreferrer" target="_blank">https://review.openstack.org/#/c/198906/</a></blockquote><div><br></div><div>I thought that's what Joe did in [1]. Am I barking up at the wrong tree?</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"><br>
<br>
What is everyone's thoughts?<br></blockquote><div><br></div><div>[1] <a href="https://review.openstack.org/#/c/195259/" target="_blank">https://review.openstack.org/#/c/195259/</a> </div><div><br></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>
Sean M. Collins<br>
</font></span><div><div><br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</div></div></blockquote></div><br></div></div>