OVSDB native get/set/clear/list functions don't support non-index lookups

[Terry Wilson]

ovs-vsctl supports looking up records in some tables by non-indexed columns.

For example,

    attr = [('connection-mode', connection_mode)]
    self.ovsdb.db_set('Controller', self.br_name, *attr).execute( check_error=True)

with the vsctl backend will run:

    ovs-vsctl set Controller $br_name connection-mode=$connection_mode

and will return the Controller for $bridge_name.

The OVSDB native version will return an error.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

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

commit bfe3b679096e73015bae6592f926b26fa427f112
Author: Terry Wilson <email address hidden>
Date: Thu Mar 19 12:43:21 2015 -0500

    Handle non-index lookups in native OVSDB backend

    ovs-vsctl get/set/clear/list can use a record_id that is not an
    index on the table being queried. For example, the Controller table
    can be queried by a bridge name.

    This patch implements the lookup table that ovs-vsctl uses to do
    these lookups.

    Change-Id: I1983c48c5839df016046ba2596c7c4affa1ebe00
    Closes-Bug: 1435567

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: neutron-pecan
Review: https://review.openstack.org/185072