Use ovsdbapp for Neutron OVSDB API

[Terry Wilson]

The OVSDB API has been split out into its own project: ovsdbapp. Neutron should use ovsdbapp, but still provide a deprecated ability to import the OVSDB API for projects that have not yet been switched over to using ovsdbapp.

[Jakub Libosvar (libosvar)]

On going awesome work here https://review.openstack.org/#/c/453014/

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/453014
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=e6333593ae6005c4b0d73d9dfda5eb47f40dd8da
Submitter: Jenkins
Branch: master

commit e6333593ae6005c4b0d73d9dfda5eb47f40dd8da
Author: Terry Wilson <email address hidden>
Date: Fri Feb 24 00:00:33 2017 -0600

    Use the ovsdbapp library

    This patch uses the ovsdbapp Python library, which is the new
    project based on the Neutron OVSDB API.

    The CLI implementation of the OVSDB API remains in the Neutron
    tree.

    Neutron continues providing the (deprecated) ability to allow
    the OVSDB API to be imported from Neutron.

    The deleted tests exist in the ovsdbapp project. More will be
    moved later, but many of the tests in the Neutron tree use
    ovs_lib, which doesn't exist in ovsdbapp so those tests will
    probably stay in the Neutron tree.

    Closes-Bug: #1684277
    Depends-On: I3d3535b1d6fe37c78a9399903b65bbd688b1c4b9
    Change-Id: Ic8c7db0e80d0ad104242322d3f1f70cab8caab92

[OpenStack Infra (hudson-openstack)]

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