<div dir="ltr"><br><div class="gmail_extra">While I have a partisan preference for OVS, my vote is that until Neutron's built-in network virtualisation suite (if we can it this way) supports both linux bridge and open vswitch, both should be given equal coverage in gate tests - and this is something we do not do currently.</div><div class="gmail_extra"><br></div><div class="gmail_extra">I understand however default values are important because they will determine the technology users will get if they just try and run devstack.</div><div class="gmail_extra">I think this is a non-issue too, but because of my partisan preference I would like to default to OVS. Attila also makes some points that in my opinion weigh more thatn Jens' counterargument - mostly because this "complexity" will be handled by devstack and is going to be totally transparent to the final user.</div><div class="gmail_extra">I believe devstack users will read at least the README files where they'll learn how to enable OVS or LinuxBridge.</div><div class="gmail_extra"><br></div><div class="gmail_extra">More inline.</div><div class="gmail_extra"><br></div><div class="gmail_extra">Salvatore</div><div class="gmail_extra"><br><div class="gmail_quote">On 10 April 2015 at 12:29, Attila Fazekas <span dir="ltr"><<a href="mailto:afazekas@redhat.com" target="_blank">afazekas@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><br>
<br>
<br>
<br>
----- Original Message -----<br>
> From: "Jens Rosenboom" <<a href="mailto:j.rosenboom@x-ion.de">j.rosenboom@x-ion.de</a>><br>
> To: "OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
</span><span class="">> Sent: Friday, April 10, 2015 10:18:38 AM<br>
> Subject: Re: [openstack-dev] [Nova][Neutron] Linuxbridge as the default in DevStack [was: Status of the nova-network<br>
> to Neutron migration work]<br>
><br>
</span><span class="">> 2015-04-10 9:05 GMT+02:00 Attila Fazekas < <a href="mailto:afazekas@redhat.com">afazekas@redhat.com</a> > :<br>
><br>
><br>
> Hi,<br>
><br>
> I do not recommend Linux bridge as default for devstack.<br>
><br>
> I think most developer does not have a switch configured with trunk ports,<br>
> or tricks for faking it in a visualized environment.<br></span></blockquote><div><br></div><div>Back in the olden days before neutron, I had indeed to use on of those cheap 30€ switches that do not even know what a tag is...<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">
><br>
><br>
> I would argue this to be a non issue. Most developers will only run single<br>
> node setups anyway.<br>
> If they setup multiple nodes connected with a switch that happens not to be<br>
> VLAN aware, it will<br>
> most likely still be VLAN transparent at the same time, so things still will<br>
> just work. This<br>
> also includes the propably most common case of multiple qemu instances<br>
> connected via a Linuxbridge<br>
> device on the host.<br></span></blockquote><div><br></div><div>I'm not sure what case you're referring to here. Nested virtualization where a bridge on the host acts as your physical bridge? </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">
<br>
</span>It is for untagged traffic only.<br>
<span class=""><br>
><br>
><br>
> I think adding some basic mtu and nat trick to devstack,<br>
> would make simpler to use the ml2/ovs/vxaln network<br>
> for devs who are not really familiar with networking.<br>
><br>
><br>
> IMHO "adding ... trick" and "make simpler" is incompatible with each other.<br>
><br>
<br>
</span>The original complain was against single node, the vms does not sees the outside network.<br>
This can be solved just by a masquerade iptables rule.<br></blockquote><div><br></div><div>I often configured such NAT rule myself, and patched devstack my local devstack repo to add them.</div><div>However, I did not find these rules very useful for running gate tests, as outbound connectivity was not required.</div><div>I do not recall exactly the reasons behind the original complains, but I seem to recall the complain was about allowing users to spin up an environment where instances would have internet connectivity with the default configuration.</div><div>Since Neutron allocates IPs from the external network for router gateway ports, without the masquerade rule mentioned by Attila this would require the user to be in control of IP addressing on that network - which is often untrue especially in corporate environments.</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
For multi-node MTU <a href="https://review.openstack.org/#/c/112523/" target="_blank">https://review.openstack.org/#/c/112523/</a>,<br>
with single node you do not really care.<br></blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5"><br>
<br>
><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>
<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>