On Thu, May 26, 2016 at 9:48 PM, Vikas Choudhary <choudharyvika...@gmail.com > wrote:
> Hi All, > > Recently, Banix observed and brought into notice this issue [1]. > > To solve this, i could think of two approaches: > 1. Modifying the libnetwork apis to get PoolID also at network creation. > OR > 2. Enhancing the /network docker api to get PoolID details also > > Problem with the first approach is that it is changing libnetwork > interface which is common for all remote drivers and thus chances of any > break-ups are high. So I preferred second one. > > Here is the patch I pushed to docker [2]. > > Once this is merged, we can easily fix this issue by tagging poolID to > neutron networks and filtering subnets at address request time based on > this information. > > Any thoughts/suggestions? > I think following the address scope proposal at [2] is the best course of action. Thanks for taking it up with Docker upstream! > > > Thanks > Vikas > > [1] https://bugs.launchpad.net/kuryr/+bug/1585572 > [2] https://github.com/docker/docker/issues/23025 > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
