>
> Hi Mark,
>
>
> If you are deploying this with OpenStack, it will be nice for you to be
> familiar
> with project Kuryr.
>
> I have written an introduction blog post about the project here:
> http://galsagie.github.io/sdn/openstack/docker/kuryr/neutron/2015/08/24/
> kuryr-part1/
>
>
> And
Hi Mark,
If you are deploying this with OpenStack, it will be nice for you to be
familiar with project Kuryr.
I have written an introduction blog post about the project here:
http://galsagie.github.io/sdn/openstack/docker/kuryr/neutron/2015/08/24/kuryr-part1/
And an Integration of Kuryr and OVN b
>
> Yes, I presume this will be the preferred way of interfacing docker with ovs?
Docker user facing APIs around networking is such that integration
with OVS will need a control plane to provide the desired multi-host
networking to work. OVN is an option for that. So OVN is one way to
integrate Do
>
> Are you talking about: https://github.com/shettyg/ovn-docker ?
Yes, I presume this will be the preferred way of interfacing docker with ovs?
>
> If so, there has been a lot of changes in docker api over the last couple of
> weeks and that code no longer works. That is one of the reason I am
Are you talking about: https://github.com/shettyg/ovn-docker ?
If so, there has been a lot of changes in docker api over the last
couple of weeks and that code no longer works. That is one of the
reason I am maintaining it out of tree - libnetwork is still
experimental and the APIs have been chan
Hi,
Can anyone point me to discussions on the status of the ovn-docker driver? It
appears to be maintained out of the ovs or docker tree. Is there any intention
to upstream it into the main docker code?
Thanks,
Mark
___
discuss mailing list
discuss@o
