Open Stack

Hello,

In such case like You described, ports will be bound with openvswitch 
mechanism driver because this agent will be found as alive on host. So 
linuxbridge mechanism driver will do nothing for binding such ports.

--
Slawek Kaplonski
slawek at kaplonski.pl

W dniu 05.01.2017 04:51, zhi napisał(a):

> Hi, Kevin. If I load openvswitch and linuxbridge mechanism drivers in 
> neutron server, and running ovs-agent in compute nodes. What does 
> openvsitch mechanism driver do? What does linuxbridge mechanism do? I 
> think there must have some differences between the openvswitch and the 
> linuxbridge mechanism driver. But I can't get the exact point about the 
> two mechanism drivers when running ovs-agent in compute nodes now.
> 
> 2017-01-04 16:16 GMT+08:00 Kevin Benton <kevin at benton.pub>:
> 
> Note that with the openvswitch and linuxbridge mechanism drivers, it 
> will be safe to have both loaded on the Neutron server at the same time 
> since each driver will only bind a port if it has an agent of that type 
> running on the host.
> 
> On Fri, Dec 30, 2016 at 1:24 PM, Sławek Kapłoński <slawek at kaplonski.pl> 
> wrote:
> Hello,
> 
> I don't know what is hierarchical port binding but about mechanism
> drivers, You should use this mechanism driver which L2 agent You are
> using on compute/network nodes. If You have OVS L2 agent then You 
> should
> have enabled openvswitch mechanism driver.
> In general both of those drivers are doing similar work on
> neutron-server side because they are checking if proper agent type is
> working on host and if other conditions required to bind port are 
> valid.
> Mechanism drivers can have also some additional informations about
> backend driver, e.g. there is info about supported QoS rule types for
> each backend driver (OVS, Linuxbridge and SR-IOV).
> 
> BTW. IMHO You should send such questions to 
> openstack at lists.openstack.org
> 
> --
> Best regards / Pozdrawiam
> Sławek Kapłoński
> slawek at kaplonski.pl
> 
> On Fri, 30 Dec 2016, zhi wrote:
> 
>> Hi, all
>> 
>> First of all. Happy New year for everyone!
>> 
>> I have a question about mechanism drivers when using ML2 driver.
>> 
>> When should I use openvswitch mechanism driver ?
>> 
>> When should I use linuxbridge mechanism driver ?
>> 
>> And, when should I use openvswitch and linuxbridge mechanism drivers ?
>> 
>> In my opinion, ML2 driver has supported hierarchical port binding. By 
>> using
>> hierarchical port binding,
>> neutron will know every binding info in network topology, isn't it? If 
>> yes,
>> where I can found the every binding info. And what the relationship 
>> between
>> hierarchical port binding and mechanism drivers?
>> 
>> 
>> Hope for your reply.
>> 
>> Thanks
>> Zhi Chang
>> __________________________________________________________________________
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: 
>> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: 
> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: 
> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev