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
sla...@kaplonski.pl
W dniu 05.01.2017 04:51, zhi
The mechanism drivers populate the vif details that tell nova how it's
supposed to setup the VM port. So the linux bridge driver tells it the port
type is linux bridge[1] and the OVS tells it that the type is OVS.
So if you have both loaded and ovs is running on the compute node. The
following
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
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
Zhi,
Selection of driver is deployment dependent. You could run or more ML2
drivers simultaneous depending upon your deployment.
Hierarchical Port Binding (HPB) facilitates multi-segmented L2 networks
where the scope of the Segmentation ID is local to a given segment.
For example - if you want
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
