[openstack-dev] [Neutron][Kuryr][kolla] - Bringing Dockers networking to Neutron
mb at us.ibm.com
Thu Jul 23 17:35:29 UTC 2015
I let the creators of the project speak for themselves but here is my take
on project Kuryr.
The goal is not to containerize Neutron or other OpenStack services. The
main objective is to use Neutron as a networking backend option for Docker.
The original proposal was to do so in the context of using containers (for
different Neutron backends or vif types). While the main objective is
fundamental to the project, the latter (use of containers in this
particular way) seems to be a tactical choice we need to make. I see
several different options available to achieve the same goal in this
Now, there is another aspect of using containers in the context of this
project that is more interesting at least to me (and I do not know if
others share this view or not) and that is the use of containers for
providing network services that are not available through libnetwork as of
now or in near future or ever. From the talks I have had with libnetwork
developers the plan is to stay with the basic networking infrastructure and
leave additional features to be developed by the community and to do so
possibly by using what else, containers.
So take the current features available in libnetwork. You mainly get
support for connectivity/isolation for multiple networks across multiple
hosts. Now if you want to route between these networks, you have to devise
a solution yourself. One possible solution would be having a router service
in a container that gets connected to say two Docker networks. Whether the
router service is implemented with the use of the current Neutron router
services or by some other solutions is something to look into and discuss
but this is a direction where I think Kuryr (did I spell it right? ;)) can
and should contribute to.
Just my 2 cents on this topic.
From: "Steven Dake (stdake)" <stdake at cisco.com>
To: "OpenStack Development Mailing List (not for usage questions)"
<openstack-dev at lists.openstack.org>, Eran Gampel
<Eran.Gampel at toganetworks.com>, Antoni Segura Puimedon
<toni at midokura.com>, Irena Berezovsky <irena at midokura.com>,
"gal.sagie at gmail.com" <gal.sagie at gmail.com>
Date: 07/23/2015 11:34 AM
Subject: Re: [openstack-dev] [Neutron][Kuryr][kolla] - Bringing Dockers
networking to Neutron
I’m not clear exactly what you plan to do with regards to building docker
containers for Neutron, but the Kolla project has developed both
linuxbridge and ovs agents as well as a complete running Neutron system
inside container technology. We can launch it AIO with docker-compose, or
alternatively it can be launched AIO or multinode with Ansible. Note we
have a complete OpenStack implementation, not just Neutron.
We would welcome additional driver support using the standard OpenStack
Note we are also in the process of adding build from source to our tree
For further background on Kolla, check out our wiki page:
From: Gal Sagie <gal.sagie at gmail.com>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" <
openstack-dev at lists.openstack.org>
Date: Wednesday, July 22, 2015 at 9:28 AM
To: "OpenStack Development Mailing List (not for usage questions)" <
openstack-dev at lists.openstack.org>, Eran Gampel <
Eran.Gampel at toganetworks.com>, Antoni Segura Puimedon <toni at midokura.com>,
Irena Berezovsky <irena at midokura.com>
Subject: [openstack-dev] [Neutron][Kuryr] - Bringing Dockers networking to
Project Kuryr is now officially part of Neutron's big tent.
Kuryr is aimed to be used as a generic docker remote driver that
connects docker to Neutron API's
and provide containerised images for the common Neutron plugins.
We also plan on providing common additional networking services API's
from other sub projects
in the Neutron big tent.
We hope to get everyone on board with this project and leverage this
joint effort for the many different solutions out there (instead of
everyone re-inventing the wheel for each different project).
We want to start doing a weekly IRC meeting to coordinate the
different requierments and
tasks, so anyone that is interested to participate please share your
and we will try to find the best time for the majority.
Remember we have people in Europe, Tokyo and US, so we won't be able
to find time that fits
The currently proposed time is Wedensday at 16:00 UTC
Please reply with your suggested time/day,
Hope to see you all, we have an interesting and important project
ahead of us
OpenStack Development Mailing List (not for usage questions)
OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
-------------- next part --------------
An HTML attachment was scrubbed...
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 105 bytes
Desc: not available
More information about the OpenStack-dev