Open Stack

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

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20161230/899e6433/attachment.pgp>