[RFE] Support multi driver pools for hybrid deployments

I'm looking forward to this feature so much!
Do you have any release plan to include this patch?

Reviewed: https://review.openstack.org/528345
Committed: https://git.openstack.org/cgit/openstack/kuryr-kubernetes/commit/?id=a83eba5fa1ebae59ee1034bf01c42c81268d23b4
Submitter: Zuul
Branch: master

commit a83eba5fa1ebae59ee1034bf01c42c81268d23b4
Author: Luis Tomas Bolivar <email address hidden>
Date: Fri Dec 15 17:56:07 2017 +0100

    Add multi pools support

    This patch adds support for nodes with different vif drivers as
    well as different pool drivers for each vif driver type.

    Closes-Bug: 1747406
    Change-Id: I842fd4b513a5f325d598d677e5008f9ea51adab9

This issue was fixed in the openstack/kuryr-kubernetes 0.5.0 release.

Reviewed: https://review.openstack.org/596672
Committed: https://git.openstack.org/cgit/openstack/kuryr-kubernetes/commit/?id=721932dc4b030640c6615781f42cc5f44c9ba640
Submitter: Zuul
Branch: master

commit 721932dc4b030640c6615781f42cc5f44c9ba640
Author: Yash Gupta <email address hidden>
Date: Mon Aug 27 17:09:38 2018 +0900

    Refactor DriverBase.get_instance()

    scope param is added to allow getting multiple independent instances
    of a driver. This is particularly useful for using same VIFPoolDriver
    implementation for multiple PodVIFDrivers (eg. NoopVIFPool may be
    used for multiple PodVIFDriver types)

    Also renames driver_alias to specific_driver to better indicate its
    function.

    Related-Bug: 1747406
    Change-Id: Iea3b65b91f362a18cca6bf9d44d938063a56118b
    Signed-off-by: Yash Gupta <email address hidden>

Reviewed: https://review.openstack.org/596673
Committed: https://git.openstack.org/cgit/openstack/kuryr-kubernetes/commit/?id=b0dfd35d76468986682a966c1fb609952fafc44f
Submitter: Zuul
Branch: master

commit b0dfd35d76468986682a966c1fb609952fafc44f
Author: Yash Gupta <email address hidden>
Date: Mon Aug 27 17:43:27 2018 +0900

    Use same pool_driver for different pod_vif_drivers

    New config option vif_pool_mapping is added and pools_vif_drivers is
    deprecated. The newer vif_pool_mapping is simply inverted mapping of
    pools_vif_drivers.
    Also, with the scoping ability added in cb2d308f84, independent
    drv_pool instances can be acquired from base driver manager.

    Earlier as a single instance of drv_pool was used by all
    pod_drivers. This meant only the pod_driver which was
    passed to drv_pool.set_vif_driver finally was used (for a given
    drv_pool).

    Please see release notes for further details.

    Related-Bug: 1747406
    Change-Id: Id0137f6b1a78e7aa3e3d3de639a5e989f4fd408c
    Signed-off-by: Yash Gupta <email address hidden>