Open Stack

Hi All,

I humbly request everybody to review this bp [1] and provide inputs once
you got some time.



Thanks
Vikas

[1] https://blueprints.launchpad.net/kuryr/+spec/address-scopes-spaces

On Sat, May 28, 2016 at 10:08 AM, Vikas Choudhary <
choudharyvikas16 at gmail.com> wrote:

> Thanks Toni, after some thought process, to me also also addressSpace
> approach making sense. We can map neutron addressScopes to docker
> addressSpaces.
>
> Have drafted a blueprint here [1]. I think i have got enough clarity on
> approach. Will be pushing a spec for this soon.
>
>
>
> Thanks
> Vikas
>
>  [1]https://blueprints.launchpad.net/kuryr/+spec/address-scopes-spaces
>
> On Sat, May 28, 2016 at 1:54 AM, Antoni Segura Puimedon <
> toni+openstackml at midokura.com> wrote:
>
>>
>>
>> On Thu, May 26, 2016 at 9:48 PM, Vikas Choudhary <
>> choudharyvikas16 at 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-request at 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-request at lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160529/42246fc7/attachment.html>