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 <
choudharyvika...@gmail.com> wrote:
> Thanks Toni, after
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:
On Thu, May 26, 2016 at 9:48 PM, Vikas Choudhary 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 /netwo
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 approac
