Fullstack: init trunk agent's driver only when necessary
Trunk driver is not needed to be initialized when "trunk"
service plugin is not enabled.
On production environments it's not possible to base on
"service_plugins" config option on L2 agent's side so this
driver is initialized always.
It cause problems on fullstack tests becasue there is race
condition between different ovs agents which consumes events
from Openvswitch monitor.
On fullstack tests however we can assume that agent's and server's
config are in sync so trunk driver can be initialized only if
"trunk" service plugin is enabled on server side.
Reviewed: https:/ /review. openstack. org/517598 /git.openstack. org/cgit/ openstack/ neutron/ commit/ ?id=806cf71eb5a f34359f8bc0c6b7 40752e53cf854f
Committed: https:/
Submitter: Zuul
Branch: master
commit 806cf71eb5af343 59f8bc0c6b74075 2e53cf854f
Author: Sławek Kapłoński <email address hidden>
Date: Fri Nov 3 09:59:04 2017 +0000
Fullstack: init trunk agent's driver only when necessary
Trunk driver is not needed to be initialized when "trunk" plugins" config option on L2 agent's side so this
service plugin is not enabled.
On production environments it's not possible to base on
"service_
driver is initialized always.
It cause problems on fullstack tests becasue there is race
condition between different ovs agents which consumes events
from Openvswitch monitor.
On fullstack tests however we can assume that agent's and server's
config are in sync so trunk driver can be initialized only if
"trunk" service plugin is enabled on server side.
Change-Id: I3ad8d6e7b8f103 867ee277078d03f 3a01c20ac0d
Closes-Bug: #1687709