<div dir="ltr">><div class="gmail_default" style="font-size:12.8000001907349px;font-family:'courier new',monospace;display:inline">Well, this is part of the motivation behind this patch. If the default is Linuxbridge, that is what </div><div class="gmail_default" style="font-size:12.8000001907349px;font-family:'courier new',monospace;display:inline">is being used in all the gate testing unless it it being explictly overridden.</div><span style="font-size:12.8000001907349px"> </span><div><span style="font-size:12.8000001907349px"><br></span></div><div><span style="font-size:12.8000001907349px">The defaults and what is tested in the gate are independent. Devstack defaults to Nova network and we don't test that at all in Neutron. :) </span></div><div><span style="font-size:12.8000001907349px"><br></span></div><div><span style="font-size:12.8000001907349px">If this change were to go through, we would likely just adjust all of the Neutron jobs to explicitly use OVS since that is what the current jobs are testing and there hasn't been any agreement in the Neutron development community to drop that. </span><span style="font-size:12.8000001907349px">If one of your goals is gate coverage of Linuxbridge, then explicitly propose another job to run with Neutron patches based on Linuxbridge. </span></div><div><span style="font-size:12.8000001907349px"><br></span></div><div><span style="font-size:12.8000001907349px">></span><span style="font-family:'courier new',monospace;font-size:12.8000001907349px">Since DVR is not enabled by default anyway (or is it?), I don't think that it will be much of an issue </span><div class="gmail_default" style="font-size:12.8000001907349px;font-family:'courier new',monospace;display:inline">if enabling it will now require changing two settings instead of one. </div><span style="font-size:12.8000001907349px"> </span><div class="gmail_default" style="font-size:12.8000001907349px;font-family:'courier new',monospace;display:inline">But having that as a second step </div><span style="font-family:'courier new',monospace;font-size:12.8000001907349px">after having done a successful initial deployment, will be a much better experience for most users than </span><span style="font-family:'courier new',monospace;font-size:12.8000001907349px">having them fail in their first contact with neutron already.</span></div><div><span style="font-family:'courier new',monospace;font-size:12.8000001907349px"><br></span></div><div><span style="font-size:12.8000001907349px">That's a pretty abrupt change for users to go through. It's misleading to start out with Linuxbridge so users become comfortable with that and then tell them they have to redeploy everything with a different vswitch to get distributed routing. </span></div><div><span style="font-size:12.8000001907349px"><br></span></div><div><span style="font-size:12.8000001907349px">Can you give some examples of how users are failing in their first contact with Neutron? </span><span style="font-size:12.8000001907349px">The Neutron API is supposed to abstract away those implementation details and devstack is supposed to make the initial OVS install and setup simple. It seems like there is an issue with one of those if people are having difficulty getting Neutron test deployments to work. If those are broken, I don't see </span><span style="font-size:12.8000001907349px">why using Linux bridge is supposed to help.</span></div><div><span style="font-size:12.8000001907349px"><br></span></div><div><span style="font-size:12.8000001907349px"><br></span></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Apr 10, 2015 at 1:34 AM, Jens Rosenboom <span dir="ltr"><<a href="mailto:j.rosenboom@x-ion.de" target="_blank">j.rosenboom@x-ion.de</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"><div dir="ltr"><div class="gmail_extra"><span>2015-04-10 9:31 GMT+02:00 Kevin Benton <span dir="ltr"><<a href="mailto:blak111@gmail.com" target="_blank">blak111@gmail.com</a>></span>:<br></span><div class="gmail_quote"><span><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"><p dir="ltr">I mentioned this in my email in the previous thread, but I am also concerned about the use of the Linux bridge plugin as the default for devstack. </p>
<p dir="ltr">It will reflect poorly on the Neutron project because we are defaulting to something that gets almost no development effort and that is not even gated on (other than unit tests). This is a risky move that can damage first-time users' opinions of the viability of OpenStack. I wouldn't feel confident about something that has defaults that could be broken at any time... even during a release. </p></blockquote></span><div><br><div class="gmail_default" style="font-family:'courier new',monospace;display:inline">Well, this is part of the motivation behind this patch. If the default is Linuxbridge, that is what<br></div><div class="gmail_default" style="font-family:'courier new',monospace;display:inline">is being used in all the gate testing unless it it being explictly overridden.</div> </div><span><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">
<p dir="ltr">Can someone point me to the list of complaints about OVS? I would rather invest time in addressing those issues rather than ignoring everything a good chunk of the neutron community has spent significant time on. </p>
<p dir="ltr">If OVS really is a non-starter because of lack of tooling and lack of deployer experience, we (the neutron community) will need to put significantly more efforts into automated testing and feature parity (e.g. re-implement DVR). </p></blockquote></span><div><div class="gmail_default" style="font-family:'courier new',monospace;display:inline">The idea is to make the entry level for using neutron networking as low as possible. Currently starting<br></div><div class="gmail_default" style="font-family:'courier new',monospace;display:inline">with neutron implicitly also requires starting with OVS, which is adding complexity that in a significant<br></div><div class="gmail_default" style="font-family:'courier new',monospace;display:inline">amount of environments is not needed. This probably includes most of the deployments that still cling to<br></div><div class="gmail_default" style="font-family:'courier new',monospace;display:inline">using nova-network, but also people looking at OpenStack for the first time. <br></div><div class="gmail_default" style="font-family:'courier new',monospace;display:inline"><br></div><div class="gmail_default" style="font-family:'courier new',monospace;display:inline">Since DVR is not enabled by default anyway (or is it?), I don't think that it will be much of an issue<br></div><div class="gmail_default" style="font-family:'courier new',monospace;display:inline">if enabling it will now require changing two settings instead of one. </div> <div class="gmail_default" style="font-family:'courier new',monospace;display:inline">But having that as a second step<br></div><div class="gmail_default" style="font-family:'courier new',monospace;display:inline">after having done a successful initial deployment, will be a much better experience for most users than<br></div><div class="gmail_default" style="font-family:'courier new',monospace;display:inline">having them fail in their first contact with neutron already.</div></div></div></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" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div><div>Kevin Benton</div></div>
</div></div>