Monitor phys_bridges to reconfigured it if created again
In case when external bridge configured in OVS agent's bridge_mappings
will be destroyed and created again (for example by running ifup-ovs
script on Centos) bridge wasn't configured by OVS agent.
That might cause broken connectivity for OpenStack's dataplane if
dataplane network also uses same bridge.
This patch adds additional ovsdb-monitor to monitor if any
of physical bridges configured in bridge_mappings was created.
If so, agent will reconfigure it to restore proper openflow rules
on it.
Reviewed: https:/ /review. openstack. org/566178 /git.openstack. org/cgit/ openstack/ neutron/ commit/ ?id=85b46cd51eb ec67d5018d8bef4 f796ee5ef4fedf
Committed: https:/
Submitter: Zuul
Branch: master
commit 85b46cd51ebec67 d5018d8bef4f796 ee5ef4fedf
Author: Sławek Kapłoński <email address hidden>
Date: Fri May 4 00:12:03 2018 +0200
Monitor phys_bridges to reconfigured it if created again
In case when external bridge configured in OVS agent's bridge_mappings
will be destroyed and created again (for example by running ifup-ovs
script on Centos) bridge wasn't configured by OVS agent.
That might cause broken connectivity for OpenStack's dataplane if
dataplane network also uses same bridge.
This patch adds additional ovsdb-monitor to monitor if any
of physical bridges configured in bridge_mappings was created.
If so, agent will reconfigure it to restore proper openflow rules
on it.
Change-Id: I9c0dc587e70327 e03be5a64522d0c 679665f79bd
Closes-Bug: #1768990