Support a mixed DPDK and non-DPDK environment

[Numan Siddique]

Now that OVN ML2 driver can read the chassis table from the OVN SB DB, we can determine the datapath type of the chassis (either normal or dpdk) using the external_ids column and use that information in port binding to support a mixed DPDP and non-DPDK environment.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/347176
Committed: https://git.openstack.org/cgit/openstack/networking-ovn/commit/?id=5be7dfeb637984f75937a21b994c1375dfa77d87
Submitter: Jenkins
Branch: master

commit 5be7dfeb637984f75937a21b994c1375dfa77d87
Author: Numan Siddique <email address hidden>
Date: Mon Jul 25 18:03:10 2016 +0530

    Support a mixed DPDK and non-DPDK environment

    ovn-controller stores the datapath type and supported interface
    types of the host in the external_ids column of the chassis table.

    When the bind_port() function is called, this patch determines the
    vif_type by reading these values from the chassis row where the port is to
    be bound.

    If the value of datapath type is 'netdev' and has 'dpdkvhostuser' in
    the supported interface types, vif_type will be set to 'vhostuser',
    else vif_type will be set to 'ovs'.

    The config param 'vif_type' is deprecated and no longer used.

    Co-Authored-By: Richard Theis <email address hidden>

    Change-Id: Ia97198a5bceb5d8d39d8556346f3709846f3c5ad
    Closes-bug: #1606458

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/networking-ovn 2.0.0.0b1 development milestone.