<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="">To expand on that a bit, I think the DVR complaints were vague because of the simple fact that the overwhelming majority were or wanted to run linuxbridge, not OVS, so DVR was a theoretical thing for them.<div class=""><br class=""></div><div class="">doug</div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Aug 19, 2015, at 2:21 PM, Salvatore Orlando <<a href="mailto:salv.orlando@gmail.com" class="">salv.orlando@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class=""><div class=""><div class="">The etherpad contains some complaints around DVR implementation that might deserve furhter exploration.<br class=""></div>However, as pointed out by Jay, the comments made leave very little room for actionable items.<br class=""></div>It would be great if the author(s) could fill in with more details.<br class=""><br class=""></div>Salvatore<br class=""></div><div class="gmail_extra"><br class=""><div class="gmail_quote">On 19 August 2015 at 23:11, Ryan Moats <span dir="ltr" class=""><<a href="mailto:rmoats@us.ibm.com" target="_blank" class="">rmoats@us.ibm.com</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class=""><p class="">One thing came up during lunch was including unit and functional testing of dual stack in the check and gate queues - I was regaled over lunch with one operator's experiences in trying to run Neutron on a dual stack system.<br class=""><br class="">Ryan Moats (regXboi)<br class=""><br class=""><tt class="">Edgar Magana <<a href="mailto:edgar.magana@workday.com" target="_blank" class="">edgar.magana@workday.com</a>> wrote on 08/19/2015 03:43:44 PM:<br class=""><br class="">> From: Edgar Magana <<a href="mailto:edgar.magana@workday.com" target="_blank" class="">edgar.magana@workday.com</a>></tt><br class=""><tt class=""><span class="">> To: "OpenStack Development Mailing List (not for usage questions)" <br class=""></span>> <<a href="mailto:openstack-dev@lists.openstack.org" target="_blank" class="">openstack-dev@lists.openstack.org</a>></tt><br class=""><tt class="">> Date: 08/19/2015 03:44 PM</tt></p><div class=""><div class="h5"><br class=""><tt class="">> Subject: Re: [openstack-dev] [Neutron] Etherpad from the Ops Meetup</tt><br class=""><tt class="">> <br class="">> Actually, there were very few requirements collected. So, your <br class="">> summary is correct.</tt><br class=""><tt class="">> <br class="">> I feel that this time we did not get a lot of input s we got during <br class="">> the Ops meet-up in Philadelphia.</tt><br class=""><tt class="">> <br class="">> I also recommend to read the burning issues ether pads, there are <br class="">> few suggestions on the networking side. Actually, I believe <br class="">> Operators has expressed in this session some good feedback that they<br class="">> probaly did not want to repeat during the networking section.</tt><br class=""><tt class="">> <br class="">> <a href="https://etherpad.openstack.org/p/PAO-ops-burning-issues" target="_blank" class="">https://etherpad.openstack.org/p/PAO-ops-burning-issues</a></tt><br class=""><tt class="">> <br class="">> Cheers,</tt><br class=""><tt class="">> <br class="">> Edgar</tt><br class=""><tt class="">> <br class="">> From: Assaf Muller<br class="">> Reply-To: "OpenStack Development Mailing List (not for usage questions)"<br class="">> Date: Wednesday, August 19, 2015 at 1:34 PM<br class="">> To: "OpenStack Development Mailing List (not for usage questions)"<br class="">> Subject: Re: [openstack-dev] [Neutron] Etherpad from the Ops Meetup</tt><br class=""><tt class="">> <br class="">> On Wed, Aug 19, 2015 at 2:52 PM, Edgar Magana <<a href="mailto:edgar.magana@workday.com" target="_blank" class="">edgar.magana@workday.com</a><br class="">> > wrote:</tt><br class=""><tt class="">> Folks,</tt><br class=""><tt class="">> <br class="">> I just want to share with you the feedback collected today during <br class="">> the networking session on Ops Meet-up:</tt><br class=""><tt class="">> <a href="https://etherpad.openstack.org/p/PAO-ops-network-model" target="_blank" class="">https://etherpad.openstack.org/p/PAO-ops-network-model</a></tt><br class=""><tt class="">> <br class="">> Special thanks to Ryan and Doug for helping on some questions.</tt><br class=""><tt class="">> <br class="">> The only action items for Neutron developers that I can spot are:</tt><br class=""></div></div><tt class="">> 1. Linux bridge + DVR / multi host</tt><br class=""><tt class="">> 2. Prevent data loss when restarting the OVS agent (The patch [1] is<span class=""><br class="">> very close to merge anyway, nothing more to do here)</span></tt><br class=""><tt class="">> 3. Work as described by [2] (Big deployers team)</tt><span class=""><br class=""><tt class="">> The rest is either polling (Who uses what feature / plugin / etc) or<br class="">> generic comments with no actionable bugs or RFEs.</tt><br class=""><tt class="">> Did I miss anything?</tt><br class=""><tt class="">> <br class="">> [1] <a href="https://review.openstack.org/#/c/182920/" target="_blank" class="">https://review.openstack.org/#/c/182920/</a></tt><br class=""><tt class="">> [2] <a href="https://etherpad.openstack.org/p/Network_Segmentation_Usecases" target="_blank" class="">https://etherpad.openstack.org/p/Network_Segmentation_Usecases</a></tt><br class=""><tt class="">> <br class="">> Cheers,</tt><br class=""><tt class="">> <br class="">> Edgar</tt><br class=""><tt 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" 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" target="_blank" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class=""></tt><br class=""><tt 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" 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" target="_blank" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class=""></tt><br class="">
</span><div class=""><br class="webkit-block-placeholder"></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>