<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div><blockquote type="cite">Sure, though on the other hand, doesn't current discussion seem to indicate that OVS with DVR is not a viable replacement for nova-network multi-host HA (eg due to complexity), and this is why folks were working towards linux bridge?</blockquote>Some openstacker doesn’t believe ovs performance is higher than linuxbridge.</div><div>So they don’t want to use OVS. Surely old OVS has many performance problems.</div><div>Currently, the problems almost might be solved. But they aren’t sure about it.</div><div>If that is a point of the discussion, we should show it to them.</div><div><br></div><div>In any case, we need to know why do they prefer linuxbridge rather than OVS.</div><div><br></div><div>Hirofumi</div><br><div><div>On 2015/04/16, at 11:09, Tom Fifield <<a href="mailto:tom@openstack.org">tom@openstack.org</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">On 16/04/15 10:54, Fox, Kevin M wrote:<br><blockquote type="cite">Yes, but.... if stuff like dvr is the only viable replacement to<br>nova-network in production, then learning the non representitive config<br>of neutron with linuxbridge might be misleading/counter productive since<br>ovs looks very very different.<br></blockquote><br>Sure, though on the other hand, doesn't current discussion seem to indicate that OVS with DVR is not a viable replacement for nova-network multi-host HA (eg due to complexity), and this is why folks were working towards linux bridge?<br><br>In essence: if linux bridge was a viable nova-network multi-host HA replacement, you'd be OK with this change?<br><br><br><blockquote type="cite">Kevin *<br>*<br>------------------------------------------------------------------------<br>*From:* Tom Fifield<br>*Sent:* Wednesday, April 15, 2015 5:58:43 PM<br>*To:* <a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a><br>*Subject:* Re: [openstack-dev] [Nova][Neutron] Linuxbridge as the<br>default in DevStack [was: Status of the nova-network to Neutron<br>migration work]<br><br><br><br>On 14/04/15 23:36, Dean Troyer wrote:<br><blockquote type="cite">On Tue, Apr 14, 2015 at 7:02 AM, Miguel Angel Ajo Pelayo<br><<a href="mailto:mangelajo@redhat.com">mangelajo@redhat.com</a> <<a href="mailto:mangelajo@redhat.com">mailto:mangelajo@redhat.com</a>>> wrote:<br><br> Why would operators install from devstack? that’s not going to be<br> the case.<br><br><br>If they do they need more help than we can give...<br></blockquote><br>So, ummm, there is actually a valid use case for ops on devstack: it's<br>part of the learning process.<br><br>In my rounds, I've had feedback from more than a few whose first<br>OpenStack experience was to run up a devstack, so they could run ps<br>aufx, brctl, iptables, etc just to see what was going on under the<br>covers before moving on to something more 'proper'.<br><br><br>While acknowledging that the primary purpose and audience of devstack is<br>and should remain development and developers, if there is something we<br>can do to improve the experience for those ops first-timers that doesn't<br>have a huge impact on devs, it would be kinda nice.<br><br>After all, one of the reasons this thread exists is because of problems<br>with that ramp up process, no?<br><br><br><blockquote type="cite"><br> I believe we should have both LB & OVS well tested, if LB is a good<br> option for<br> some operators willing to migrate from nova, that’s great, let’s<br> make sure LB<br> is perfectly tested upstream.<br><br><br>+1<br><br> But by doing such change we can’t let OVS code rot and we would be<br> neglecting<br> a big customer base which is now making use of the openvswitch<br> mechanism.<br> (may be I’m miss understanding the scope of the change).<br><br><br>Changing DevStack's default doesn't remove anything OVS-related, nor<br>does it by itself remove any OVS jobs. It gives everyone who is happy<br>with nova-net (or more correctly doesn't think about it) a new default<br>that changes their experience the least for when nova-net disappears.<br><br>dt<br><br>--<br><br>Dean Troyer<br><a href="mailto:dtroyer@gmail.com">dtroyer@gmail.com</a> <<a href="mailto:dtroyer@gmail.com">mailto:dtroyer@gmail.com</a>><br><br><br>__________________________________________________________________________<br>OpenStack Development Mailing List (not for usage questions)<br>Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org">OpenStack-dev-request@lists.openstack.org</a>?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></blockquote><br>__________________________________________________________________________<br>OpenStack Development Mailing List (not for usage questions)<br>Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org">OpenStack-dev-request@lists.openstack.org</a>?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>__________________________________________________________________________<br>OpenStack Development Mailing List (not for usage questions)<br>Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe<br>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev<br><br></blockquote><br>__________________________________________________________________________<br>OpenStack Development Mailing List (not for usage questions)<br>Unsubscribe:<span class="Apple-converted-space"> </span><a href="mailto:OpenStack-dev-request@lists.openstack.org">OpenStack-dev-request@lists.openstack.org</a>?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></div></blockquote></div><br></body></html>