ovsdb managers shouldn't be erased/overwritten

[Isaku Yamahata]

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.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/357528

[OpenStack Infra (hudson-openstack)]

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 <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
    Change-Id: Ibf9bd02fac3070d166546cac478ef984e4e43f28
    Co-Authored-By: sridhargaddam <email address hidden>
    Co-Authored-By: Terry Wilson <email address hidden>

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/newton
Review: https://review.openstack.org/403672

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/403672
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=e41cf43fc19458e672906c777d6656f08fdcd3f4
Submitter: Jenkins
Branch: stable/newton

commit e41cf43fc19458e672906c777d6656f08fdcd3f4
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
    Change-Id: Ibf9bd02fac3070d166546cac478ef984e4e43f28
    Co-Authored-By: sridhargaddam <email address hidden>
    Co-Authored-By: Terry Wilson <email address hidden>
    (cherry picked from commit 7d42176853c80545df46c3fa593d7816f12e57cf)

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/neutron 10.0.0.0b2 development milestone.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/neutron 9.2.0 release.