Reviewed: https://review.openstack.org/357528
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=7d42176853c80545df46c3fa593d7816f12e57cf
Submitter: Jenkins
Branch: master
commit 7d42176853c80545df46c3fa593d7816f12e57cf
Author: Isaku Yamahata <isaku.yamah...@intel.com>
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
Change-Id: Ibf9bd02fac3070d166546cac478ef984e4e43f28
Co-Authored-By: sridhargaddam <sgad...@redhat.com>
Co-Authored-By: Terry Wilson <twil...@redhat.com>
** Changed in: neutron
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1614766
Title:
ovsdb managers shouldn't be erased/overwritten
Status in neutron:
Fix Released
Bug description:
neutron(ovs or dhcp) agent with native ovslib sets to its own ovsdb
managers.
In some use cases, cloud admin sets ovsdb managers. e.g. monitoring/debug
purses, sdn controller.
neutron agents shouldn't erase those settings.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1614766/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
