Short-Term fix for overlapping cidrs using docker options
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kuryr |
Fix Committed
|
Undecided
|
Unassigned |
Bug Description
https:/
Dear bug triager. This bug was created since a commit was marked with DOCIMPACT.
Your project "openstack/kuryr" is set up so that we directly report the documentation bugs against it. If this needs changing, the docimpact-group option needs to be added for the project. You can ask the OpenStack infra team (#openstack-infra on freenode) for help if you need to.
commit 709fede534ec15e
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.
foo
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.
bar
At ``/IpamDriver.
corresponding pool name received from the libnetwork as explained above.
Please refer https:/
TODO: unit test cases covering docker option scenario
DocImpact
Change-Id: I7090027e68e8c7
Closes-bug: #1585572
Changed in kuryr: | |
status: | New → In Progress |
Both http:// docs.openstack. org/developer/ kuryr/readme. html#limitation s and http:// docs.openstack. org/developer/ kuryr-libnetwor k/readme. html are updating for this.
We can mark bug status now.