[Openstack-operators] neutron network configuration: linux bridges

George Shuklin george.shuklin at gmail.com
Thu Aug 28 12:18:54 UTC 2014

On 08/28/2014 02:57 PM, Assaf Muller wrote:
> ----- Original Message -----
>> I found something strange I can't solve by myself.
>> Sometimes I getting configuration where VMs traffic get to the gre
>> tunnes via following sequence: tap->qbr->qvb->qvo->br-int->br-tun->eth0.
>> It described here:
>> http://docs.openstack.org/grizzly/openstack-network/admin/content/under_the_hood_openvswitch.html
>> But sometimes I getting very different configuration:
>> tap->br-int->br-tun->eth0. It working, and working fine. And I just
>> can't find option or configuration difference, or combination of both
>> which cause switching between 'simple' and 'normal' scheme. I feel like
>> I don't understand something basic and something important.
>> Any ideas? Thanks!
> It depends on the vif_driver = nova.virt.libvirt.vif.LibvirtGenericVIFDriver
> option in nova.conf.
In my case in both cases (with qbr/qvb/qvo and without) nova-compute 
starts without defined vif_driver. I enable debug (in both cases) and 
debug config print says that 
libvirt_vif_driver=nova.virt.libvirt.vif.LibvirtGenericVIFDriver, and 
there is no notice about just 'vif_driver'. Is any other options related 
to this? And what values can be in vif_driver except 


More information about the OpenStack-operators mailing list