[neutron] Use the same network interface with multiple ML2 mechanism drivers

Slawek Kaplonski skaplons at redhat.com
Mon Nov 9 07:36:28 UTC 2020


Dnia niedziela, 8 listopada 2020 04:06:50 CET Gabriel Omar Gamero Montenegro 
> Dear all,
> I know that ML2 Neutron core plugin is designed to
> support multiple mechanism and type drivers simultaneously.
> But I'd like to know: is it possible to use the
> same network interface configured with different
> ML2 mechanism drivers?
> I'm planning to use openvswitch and linuxbridge as
> mechanism drivers along with VLAN as type driver.
> Could it be possible to have the following
> configuration for that purpose?:
> ml2_conf.ini:
> [ml2]
> mechanism_drivers = openvswitch,linuxbridge
> [ml2_type_vlan]
> network_vlan_ranges = physnet1:40:60,physnet2:60:80
> eth3 is a port of the provider bridge:
> ovs-vsctl add-port br-provider eth3
> openvswitch_agent.ini:
> [ovs]
> bridge_mappings = physnet1:br-provider
> linuxbridge_agent.ini:
> [linux_bridge]
> physical_interface_mappings = physnet2:eth3

I don't think it's will work because You would need to have same interface in 
the ovs bridge (br-provider) and use it by linuxbridge.
But TBH this is a bit strange configuration for me. I can imaging different 
computes which are using different backends. But why You want to use 
linuxbridge and openvswitch agents together on same compute node?

> If it's mandatory to use different network interfaces
> any guide or sample reference about implementing
> multiple mechanism drivers would be highly appreciated.
> Thanks in advance,
> Gabriel Gamero

Slawek Kaplonski
Principal Software Engineer
Red Hat

More information about the openstack-discuss mailing list