[openstack-dev] [Nova][Neutron] Linuxbridge as the default in DevStack [was: Status of the nova-network to Neutron migration work]
afazekas at redhat.com
Fri Apr 10 10:29:27 UTC 2015
----- Original Message -----
> From: "Jens Rosenboom" <j.rosenboom at x-ion.de>
> To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org>
> Sent: Friday, April 10, 2015 10:18:38 AM
> Subject: Re: [openstack-dev] [Nova][Neutron] Linuxbridge as the default in DevStack [was: Status of the nova-network
> to Neutron migration work]
> 2015-04-10 9:05 GMT+02:00 Attila Fazekas < afazekas at redhat.com > :
> I do not recommend Linux bridge as default for devstack.
> I think most developer does not have a switch configured with trunk ports,
> or tricks for faking it in a visualized environment.
> I would argue this to be a non issue. Most developers will only run single
> node setups anyway.
> If they setup multiple nodes connected with a switch that happens not to be
> VLAN aware, it will
> most likely still be VLAN transparent at the same time, so things still will
> just work. This
> also includes the propably most common case of multiple qemu instances
> connected via a Linuxbridge
> device on the host.
It is for untagged traffic only.
> I think adding some basic mtu and nat trick to devstack,
> would make simpler to use the ml2/ovs/vxaln network
> for devs who are not really familiar with networking.
> IMHO "adding ... trick" and "make simpler" is incompatible with each other.
The original complain was against single node, the vms does not sees the outside network.
This can be solved just by a masquerade iptables rule.
For multi-node MTU https://review.openstack.org/#/c/112523/,
with single node you do not really care.
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
More information about the OpenStack-dev