Isaku Yamahata 7d42176853 ovsdb: don't erase existing ovsdb managers ... The current existing agent erases already set ovsdb managers entries. In some use cases, cloud admin sets ovsdb managers. eg, for SDN controllers or monitoring purpose. Neutron agent shouldn't unconditionally erase the existing ovsdb managers. This patch implements a new api add_manager (along with get_manager and remove_manager) to the ovsdb api which will allow us to configure a manager on a switch without overriding the existing managers. Closes-Bug: #1614766 Change-Id: Ibf9bd02fac3070d166546cac478ef984e4e43f28 Co-Authored-By: sridhargaddam <sgaddam@redhat.com> Co-Authored-By: Terry Wilson <twilson@redhat.com>		2016-11-23 07:21:08 +00:00
..
__init__.py	Add fullstack cross-process port/ip address fixtures	2016-03-28 10:16:39 -04:00
ip_address.py	Add fullstack cross-process port/ip address fixtures	2016-03-28 10:16:39 -04:00
ip_network.py	Add fullstack cross-process port/ip address fixtures	2016-03-28 10:16:39 -04:00
port.py	ovsdb: don't erase existing ovsdb managers	2016-11-23 07:21:08 +00:00
resource_allocator.py	Use ensure_tree from oslo_utils.fileutils	2016-11-05 00:00:31 -07:00