[ovs-discuss] status of ovn-docker

Gal Sagie gal.sagie at gmail.com
Wed Oct 14 08:49:48 UTC 2015

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:

And an Integration of Kuryr and OVN blog post here:

In short Kuryr maps Docker APIs to Neutron API so you can use any Neutron
plugin for implementing
containers networking. (and OVN/OVS included)
We also plan to support special use cases for nested containers in VM (that
can expose OVN
feature of defining parent and child logical ports for this same use case)

We are now working as well on modifying all the changes needed due to
Docker 1.9 API changes.

Let me know if you have any questions.


On Tue, Oct 13, 2015 at 7:18 PM, Gurucharan Shetty <shettyg at nicira.com>

> >
> > 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 Docker with OVS. It is not necessarily the only way as there
> are a lot of other people integrating Docker with OVS with their own
> control plane.
> >>
> >> 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 changing very often and it does not make sense for openvswitch to
> >> maintain experimental code.
> >>
> >> Docker 1.9 will likely remove the experimental tag. When that happens,
> I will
> >> get the code reviewed in the openvswitch mailing list to add it to
> >> openvswitch repo.
> >
> > How come it will not get upstreamed into the docker repo? Does this mean
> > that some special configuration will need be done in docker to get this
> > working?
> Docker's libnetwork works with REST APIs. So the driver, as long as it
> implements all the REST APIs that Docker expects can reside
> independently of Docker daemon. One way to install that driver is via
> OVN packaging.
> >
> >
> _______________________________________________
> discuss mailing list
> discuss at openvswitch.org
> http://openvswitch.org/mailman/listinfo/discuss

Best Regards ,

The G.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openvswitch.org/pipermail/ovs-discuss/attachments/20151014/278a0fad/attachment-0002.html>

More information about the discuss mailing list