From 857345c9e21a044b3e2a9cd7b070e34bd75c27fd Mon Sep 17 00:00:00 2001 From: Mike Kolesnik Date: Thu, 26 Mar 2015 15:35:05 +0200 Subject: [PATCH] Added note about removing bridge from mappings A bridge removed from mappings is not managed by the OVS agent anymore, but continues to be connected to the integration bridge. Added a note about it in the config so that deployers make sure they don't end up in a sticky situation. Change-Id: I8992f842046651e0f231c6bf08b65efa07056757 Related-bug: #1436267 --- etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini | 3 +++ 1 file changed, 3 insertions(+) diff --git a/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini b/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini index 072bd7293..974ac58ed 100644 --- a/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini +++ b/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini @@ -32,6 +32,9 @@ # port. All physical networks configured on the server should have # mappings to appropriate bridges on each agent. # +# Note: If you remove a bridge from this mapping, make sure to disconnect it +# from the integration bridge as it won't be managed by the agent anymore. +# # bridge_mappings = # Example: bridge_mappings = physnet1:br-eth1 -- 2.45.2