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 <email address hidden>
Co-Authored-By: Terry Wilson <email address hidden>
Reviewed: https:/ /review. openstack. org/357528 /git.openstack. org/cgit/ openstack/ neutron/ commit/ ?id=7d42176853c 80545df46c3fa59 3d7816f12e57cf
Committed: https:/
Submitter: Jenkins
Branch: master
commit 7d42176853c8054 5df46c3fa593d78 16f12e57cf
Author: Isaku Yamahata <email address hidden>
Date: Thu Aug 18 15:32:12 2016 -0700
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 d166546cac478ef 984e4e43f28
Change-Id: Ibf9bd02fac3070
Co-Authored-By: sridhargaddam <email address hidden>
Co-Authored-By: Terry Wilson <email address hidden>