Comment 11 for bug 1585572

Reviewed: https://review.openstack.org/331050
Committed: https://git.openstack.org/cgit/openstack/kuryr/commit/?id=709fede534ec15e4f260c78019083aff9cf19282
Submitter: Jenkins
Branch: master

commit 709fede534ec15e4f260c78019083aff9cf19282
Author: vikaschoudhary16 <email address hidden>
Date: Fri Jun 17 16:23:34 2016 +0530

    Short-Term fix for overlapping cidrs using docker options

    A quick alternative solution, until PRs to upstream Docker get accepted,
    can be Docker user passing pool name to both Kuryr ipam driver and
    Kuryr network driver using corresponding network and ipam options
    respectively:

           $sudo docker network create --driver=kuryr --ipam-driver=kuryr \
           --subnet 10.0.0.0/16 --ip-range 10.0.0.0/24 \
           -o neutron.pool.name=neutron_pool1 \
           --ipam-opt=neutron.pool.name=neutron_pool1 \
           foo
          eddb51ebca09339cb17aaec05e48ffe60659ced6f3fc41b020b0eb506d364

    Now Docker user creates another network with same cidr as the previous,
    i.e 10.0.0.0/16, but with different pool name, neutron_pool2:

        $sudo docker network create --driver=kuryr --ipam-driver=kuryr \
           --subnet 10.0.0.0/16 --ip-range 10.0.0.0/24 \
           -o neutron.pool.name=neutron_pool2 \
           --ipam-opt=neutron.pool.name=neutron_pool2 \
           bar
        397badb51ebca09339cb17aaec05e48ffe60659ced6f3fc41b020b0eb506d786

    At ``/IpamDriver.RequestAddress``, correct subnet will be filtered out using
    corresponding pool name received from the libnetwork as explained above.

    Please refer https://review.openstack.org/#/c/326894/6

    TODO: unit test cases covering docker option scenario

    DocImpact
    Change-Id: I7090027e68e8c78219a387da66e1bd30be900ab1
    Closes-bug: #1585572