<div dir="ltr">On Fri, Apr 10, 2015 at 1:03 PM, Sean M. Collins <span dir="ltr"><<a href="mailto:sean@coreitpro.com" target="_blank">sean@coreitpro.com</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">We already tried to make Neutron the default with OVS - and the results<br>
were not good[1].<br>
<br>
Operators who are currently not using Neutron have said that they do<br>
not want to learn both Neutron and also Open vSwitch at the same time.<br>
<br>
This was documented at the operator's summit. We clearly have a<br>
stumbling block - Open vSwitch.<br>
<br>
<a href="https://etherpad.openstack.org/p/PHL-ops-nova-feedback" target="_blank">https://etherpad.openstack.org/p/PHL-ops-nova-feedback</a><br>
<br>
<a href="https://etherpad.openstack.org/p/PHL-ops-OVS" target="_blank">https://etherpad.openstack.org/p/PHL-ops-OVS</a><br>
<br>
Based on discussions we had at the QA sprint, the idea is to start with<br>
a very simple Neutron configuration in DevStack, so that we can remove<br>
nova-network as the default. The argument is that the people<br>
who are still using nova-network are comfortable with Linux Bridge, and<br>
that having Linux Bridge as the default Neutron agent will serve as<br>
a "bridge" (no pun intended) into the Neutron world.<br>
<br>
There will be *clear* documentation that this is a very simplistic<br>
model, and it will be made obvious that for more advanced scenarios you<br>
will need to configure your local.conf to use the Open vSwitch agent.<br>
<br>
I've spoken with Sean Dague about testing Linux Bridge and<br>
the idea is that we should have test coverage of both OVS and Linux<br>
Bridge, and that currently there is a gap with Linux Bridge. I think<br>
that it's OK if we override the default at the gate to run OVS, since<br>
that has the most test coverage and will cause the least disruption.<br>
There will be jobs created, that will test Linux Bridge similar to how<br>
Open vSwitch is tested at the gate today.<br>
<br>
As a DevStack user, I would like to see Neutron as the default. After<br>
making Neutron the default, the changes needed for the local.conf file<br>
for me to run my mechanism driver of choice is significantly smaller<br>
than the changes needed today for my local.conf/localrc to<br>
disable Nova-Network, enable Neutron, and run my mechanism driver of choice.<br>
<br>
If Linux Bridge being the default is the way to make the above happen,<br>
so be it.<br>
<br></blockquote><div>++, well said Sean. I support what's being done here.<br> <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
[1]: <a href="https://review.openstack.org/#/c/153208/" target="_blank">https://review.openstack.org/#/c/153208/</a><br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
Sean M. Collins<br>
</font></span><div class="HOEnZb"><div class="h5"><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>
</div></div></blockquote></div><br></div></div>