Re: [openstack-dev] [Neutron][Kuryr][kolla] - Bringing Dockers networking to Neutron
On Fri, Jul 24, 2015 at 12:02 AM, Mohammad Banikazemi wrote: > "Daneyon Hansen (danehans)" wrote on 07/23/2015 > 03:40:38 PM: > >> From: "Daneyon Hansen (danehans)" >> To: "OpenStack Development Mailing List (not for usage questions)" >> , Mohammad Banikazemi/Watson/ >> IBM@IBMUS, "Steven Dake (stdake)" >> Cc: Eran Gampel , Irena Berezovsky >> >> Date: 07/23/2015 03:45 PM >> Subject: Re: [openstack-dev] [Neutron][Kuryr][kolla] - Bringing >> Dockers networking to Neutron >> >> From: Antoni Segura Puimedon >> Reply-To: "OpenStack Development Mailing List (not for usage questions)" < >> openstack-dev@lists.openstack.org> >> Date: Thursday, July 23, 2015 at 11:16 AM >> To: Mohammad Banikazemi , "Steven Dake (stdake)" < >> std...@cisco.com> >> Cc: Eran Gampel , "OpenStack >> Development Mailing List (not for usage questions)" > d...@lists.openstack.org>, Irena Berezovsky >> Subject: Re: [openstack-dev] [Neutron][Kuryr][kolla] - Bringing >> Dockers networking to Neutron >> >> Why is a separate OpenStack project needed to contribute to >> libnetwork? I would think the Neutron community would follow the >> libnetwork contrib guidelines and submit the code. When I talked with the libnetwork people, my original goal being to make a libnetwork in tree driver before libnetwork was announced at Docker Con, it was made clear to me that third party network providers like weave, calico and Kuryr should be plugins for the remote driver and strictly out of tree. >> > > While there may be contributions to docker/libnetwork at some point, the > project is not about contributing to libnetwork. For example, the Neutron > driver itself won't be part of the docker or libnetwork tree. It is for what I stated above and Mohammad comes to the same conclusion as I did. The external providers must live apart from libnetwork and we must work together with other external providers in the future to better or increase the surface of the plugin interface as common usage patterns emerge and are seen as valuable by a sizable part of the libnetwork community. > Making other > OpenStack and Neutron services available for use by containers may be a good > reason for having it under the OpenStack and Neutron umbrella but I think > one can debate where a project fits best. My reason for this is that Kuryr aims to bring all the power and flexibility of the Neutron networking to Docker containers and I can't think of any community more fit to do so than the Neutron community itself. Neutron has a mature codebase that provides services that can be useful for container users. Services that are not commonly not available to them via an API as convenient and flexible as Neutron is. That is why I think that it is not just those users of Neutron that are now looking at Docker that will find Kuryr to be a natural match, but I also expect users starting to scale up and optimize their growing container deployments to find Kuryr (by its exposure of the Neutron goods) to bring them an interesting set of tools for their larger and fine tuned container based deployments. > > Best, > > Mohammad > > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@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-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron][Kuryr][kolla] - Bringing Dockers networking to Neutron
"Daneyon Hansen (danehans)" wrote on 07/23/2015 03:40:38 PM: > From: "Daneyon Hansen (danehans)" > To: "OpenStack Development Mailing List (not for usage questions)" > , Mohammad Banikazemi/Watson/ > IBM@IBMUS, "Steven Dake (stdake)" > Cc: Eran Gampel , Irena Berezovsky > > Date: 07/23/2015 03:45 PM > Subject: Re: [openstack-dev] [Neutron][Kuryr][kolla] - Bringing > Dockers networking to Neutron > > From: Antoni Segura Puimedon > Reply-To: "OpenStack Development Mailing List (not for usage questions)" < > openstack-dev@lists.openstack.org> > Date: Thursday, July 23, 2015 at 11:16 AM > To: Mohammad Banikazemi , "Steven Dake (stdake)" < > std...@cisco.com> > Cc: Eran Gampel , "OpenStack > Development Mailing List (not for usage questions)" d...@lists.openstack.org>, Irena Berezovsky > Subject: Re: [openstack-dev] [Neutron][Kuryr][kolla] - Bringing > Dockers networking to Neutron > > Why is a separate OpenStack project needed to contribute to > libnetwork? I would think the Neutron community would follow the > libnetwork contrib guidelines and submit the code. > While there may be contributions to docker/libnetwork at some point, the project is not about contributing to libnetwork. For example, the Neutron driver itself won't be part of the docker or libnetwork tree. Making other OpenStack and Neutron services available for use by containers may be a good reason for having it under the OpenStack and Neutron umbrella but I think one can debate where a project fits best. Best, Mohammad __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron][Kuryr][kolla] - Bringing Dockers networking to Neutron
> $ docker -d --kv-store=consul:localhost:8500 -- > label=com.docker.network.driver.kuryr.bind_interface=eth0 -- > label=com.docker.network.driver.kuryr.neutron_api=10.10.10.10 > --label=com.docker.network.driver.kuryr.token=AUTH_tk713d067336d21348bcea1ab220965485 Toni, Why do you want to have this configuration parameters known to docker? Docker uses a plugin through the libnetwork remote driver. What that plugin does and how for example it gets to the Neutron server is what the plugin has to deal with. No? I can see some information regarding IP address management may be relevant to docker and I see the use of labels but think other parameters should not be of concern to docker. You have referred to use of an authentication token. I think that is a possible place were labels can be eventually used for identifying different tenants/users but that requires a longer discussion. Best, Mohammad __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron][Kuryr][kolla] - Bringing Dockers networking to Neutron
From: Antoni Segura Puimedon mailto:toni+openstac...@midokura.com>> Reply-To: "OpenStack Development Mailing List (not for usage questions)" mailto:openstack-dev@lists.openstack.org>> Date: Thursday, July 23, 2015 at 11:16 AM To: Mohammad Banikazemi mailto:m...@us.ibm.com>>, "Steven Dake (stdake)" mailto:std...@cisco.com>> Cc: Eran Gampel mailto:eran.gam...@toganetworks.com>>, "OpenStack Development Mailing List (not for usage questions)" mailto:openstack-dev@lists.openstack.org>>, Irena Berezovsky mailto:ir...@midokura.com>> Subject: Re: [openstack-dev] [Neutron][Kuryr][kolla] - Bringing Dockers networking to Neutron On Thu, Jul 23, 2015 at 7:35 PM, Mohammad Banikazemi mailto:m...@us.ibm.com>> wrote: 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 regard. Thanks Mohammad. It is as you say, the goal of Kuryr to provide Docker with a new libnetwork remote driver that is powered by Neutron, not a containerization of Neutron. Kuryr deployments as you point out, may opt to point to a Neutron that is containerized, and for that I was looking at using Kolla. However, that is just deployment and I consider it to be something up to the deployer (of course, we'll make Kuryr containerizable and part of Kolla :-) ). The design for interaction/configuration is not yet final, as I still have to push drafts for the blueprints and get comments, but my initial idea is that you will configure docker to pass the configuration of which device to take hold of for the overlay and where the neutron api are in the following way. $ docker -d --kv-store=consul:localhost:8500 --label=com.docker.network.driver.kuryr.bind_interface=eth0 --label=com.docker.network.driver.kuryr.neutron_api=10.10.10.10 --label=com.docker.network.driver.kuryr.token=AUTH_tk713d067336d21348bcea1ab220965485 Why is a separate OpenStack project needed to contribute to libnetwork? I would think the Neutron community would follow the libnetwork contrib guidelines and submit the code. Another possibility is that those values were passed as env variables or plain old configuration files. 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. You got that right. The idea is indeed to get the containers networked via libnetwork that, as you point out, was left intentionally simple to be developed by the community; then we want to make make: a) Kuryr get the containers to networks that have been pre-configured with advanced networking (lb, sec groups, etc). Being able to perform changes on those networks via neutron after the fact as well. For example the container orchestration software could create a Neutron network with a load balancer and a FIP, start containers on that network and add them to the load balancer. b) Via the usage of either docker labels on `docker run` make Kuryr implicitly set up Neutron networks/topologies. Yup, you spelled it well. In Czech it is Kurýr, but for project purposes I dropped the "´" Thanks a lot for contributing and I'm very happy to see that you got a very good sense for the direction we are taking. I'm looking forward to meet you all in the community meetings! Just my 2 cents on this topic. Best, Mohammad [Inactive hide details fo
Re: [openstack-dev] [Neutron][Kuryr][kolla] - Bringing Dockers networking to Neutron
this topic. >> >> Best, >> >> Mohammad >> >> >> [image: Inactive hide details for "Steven Dake (stdake)" ---07/23/2015 >> 11:34:09 AM---Gal, I’m not clear exactly what you plan to do wi]"Steven >> Dake (stdake)" ---07/23/2015 11:34:09 AM---Gal, I’m not clear exactly what >> you plan to do with regards to building docker containers for Neutro >> >> From: "Steven Dake (stdake)" >> To: "OpenStack Development Mailing List (not for usage questions)" < >> openstack-dev@lists.openstack.org>, Eran Gampel < >> eran.gam...@toganetworks.com>, Antoni Segura Puimedon , >> Irena Berezovsky , "gal.sa...@gmail.com" < >> gal.sa...@gmail.com> >> Date: 07/23/2015 11:34 AM >> Subject: Re: [openstack-dev] [Neutron][Kuryr][kolla] - Bringing Dockers >> networking to Neutron >> -- >> >> >> >> Gal, >> >> 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 >> gerrit workflow. >> >> >> *https://github.com/stackforge/kolla/tree/master/docker/centos/binary/neutron* >> <https://github.com/stackforge/kolla/tree/master/docker/centos/binary/neutron> >> >> Note we are also in the process of adding build from source to our tree >> here: >> >> >> *https://github.com/stackforge/kolla/tree/master/docker/centos/source/neutron* >> <https://github.com/stackforge/kolla/tree/master/docker/centos/source/neutron> >> >> For further background on Kolla, check out our wiki page: >> >> *https://wiki.openstack.org/wiki/Kolla* >> <https://wiki.openstack.org/wiki/Kolla> >> > > Hi Steven, > > I'm glad to see you in this thread. > > The goal of Kuryr is as pointed above by Mohammad (I added a bit to it). > This other goal of getting additional > drivers for Neutron in Kolla is something that I've been looking at for a > while and, while I can only speak for MidoNet, > I think it is something that all of the Neutron vendors should be looking > to provide > > I have been playing with kolla a bit and I have it on my list to have a > Neutron container with the MidoNet plugin > and a nova compute container with the MidoNet Host Agent. I'll be reaching > out on irc for help with that ;-) > > > Best regards, > > Antoni Segura Puimedon > > > >> >> Best wishes, >> -steve >> >> *From: *Gal Sagie <*gal.sa...@gmail.com* > >> *Reply-To: *"OpenStack Development Mailing List (not for usage >> questions)" <*openstack-dev@lists.openstack.org* >> > >> *Date: *Wednesday, July 22, 2015 at 9:28 AM >> *To: *"OpenStack Development Mailing List (not for usage questions)" < >> *openstack-dev@lists.openstack.org* >, >> Eran Gampel <*eran.gam...@toganetworks.com* >> >, Antoni Segura Puimedon < >> *t...@midokura.com* >, Irena Berezovsky < >> *ir...@midokura.com* > >> *Subject: *[openstack-dev] [Neutron][Kuryr] - Bringing Dockers >> networking to Neutron >> >> >> Hello Everyone, >> >> 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 time preference >> and we will try to find the best time for the majority. >> >> Remember we have p
Re: [openstack-dev] [Neutron][Kuryr][kolla] - Bringing Dockers networking to Neutron
On Thu, Jul 23, 2015 at 7:35 PM, Mohammad Banikazemi wrote: > 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 regard. > Thanks Mohammad. It is as you say, the goal of Kuryr to provide Docker with a new libnetwork remote driver that is powered by Neutron, not a containerization of Neutron. Kuryr deployments as you point out, may opt to point to a Neutron that is containerized, and for that I was looking at using Kolla. However, that is just deployment and I consider it to be something up to the deployer (of course, we'll make Kuryr containerizable and part of Kolla :-) ). The design for interaction/configuration is not yet final, as I still have to push drafts for the blueprints and get comments, but my initial idea is that you will configure docker to pass the configuration of which device to take hold of for the overlay and where the neutron api are in the following way. $ docker -d --kv-store=consul:localhost:8500 --label=com.docker.network.driver.kuryr.bind_interface=eth0 --label=com.docker.network.driver.kuryr.neutron_api=10.10.10.10 --label=com.docker.network.driver.kuryr.token=AUTH_tk713d067336d21348bcea1ab220965485 Another possibility is that those values were passed as env variables or plain old configuration files. > > 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. > You got that right. The idea is indeed to get the containers networked via libnetwork that, as you point out, was left intentionally simple to be developed by the community; then we want to make make: a) Kuryr get the containers to networks that have been pre-configured with advanced networking (lb, sec groups, etc). Being able to perform changes on those networks via neutron after the fact as well. For example the container orchestration software could create a Neutron network with a load balancer and a FIP, start containers on that network and add them to the load balancer. b) Via the usage of either docker labels on `docker run` make Kuryr implicitly set up Neutron networks/topologies. Yup, you spelled it well. In Czech it is Kurýr, but for project purposes I dropped the "´" Thanks a lot for contributing and I'm very happy to see that you got a very good sense for the direction we are taking. I'm looking forward to meet you all in the community meetings! > > Just my 2 cents on this topic. > > Best, > > Mohammad > > > [image: Inactive hide details for "Steven Dake (stdake)" ---07/23/2015 > 11:34:09 AM---Gal, I’m not clear exactly what you plan to do wi]"Steven > Dake (stdake)" ---07/23/2015 11:34:09 AM---Gal, I’m not clear exactly what > you plan to do with regards to building docker containers for Neutro > > From: "Steven Dake (stdake)" > To: "OpenStack Development Mailing List (not for usage questions)" < > openstack-dev@lists.openstack.org>, Eran Gampel < > eran.gam...@toganetworks.com>, Antoni Segura Puimedon , > Irena Berezovsky , "gal.sa...@gmail.com" < > gal.sa...@gmail.com> > Date: 07/23/2015 11:34 AM > Subject: Re: [openstack-dev] [Neutron][Kuryr][kolla] - Bringing Dockers > ne
Re: [openstack-dev] [Neutron][Kuryr][kolla] - Bringing Dockers networking to Neutron
For my low-orbit perspective (I would have lied if I said 10,000 or 30,000 ft!) Kuryr's ultimate goal is to provide: 1) a container-oriented set of neutron plugins and drivers (you know the ML2 driver, a l3 svc plugin, a lbaas driver, etc. etc.) 2) possibly (I'm not sure if that's the case) control plane elements specifically designed to work with containers In that respect, I tend to believe that there might be a good relationship between the two projects, with Kolla providing containers for the control plane elements that Kuryr wants to deploy. Probably Kuryr (which at the moment is just a little more than the output of cookiecutter) does not want to be in the business of building container, as well as (in my opinion) Kolla does not want to be in the container networks business. Salvatore On 23 July 2015 at 18:35, Mohammad Banikazemi wrote: > 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 regard. > > 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. > > Best, > > Mohammad > > > [image: Inactive hide details for "Steven Dake (stdake)" ---07/23/2015 > 11:34:09 AM---Gal, I’m not clear exactly what you plan to do wi]"Steven > Dake (stdake)" ---07/23/2015 11:34:09 AM---Gal, I’m not clear exactly what > you plan to do with regards to building docker containers for Neutro > > From: "Steven Dake (stdake)" > To: "OpenStack Development Mailing List (not for usage questions)" < > openstack-dev@lists.openstack.org>, Eran Gampel < > eran.gam...@toganetworks.com>, Antoni Segura Puimedon , > Irena Berezovsky , "gal.sa...@gmail.com" < > gal.sa...@gmail.com> > Date: 07/23/2015 11:34 AM > Subject: Re: [openstack-dev] [Neutron][Kuryr][kolla] - Bringing Dockers > networking to Neutron > -- > > > > Gal, > > 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 > gerrit workflow. > > > *https://github.com/stackforge/kolla/tree/master/docker/centos/binary/neutron* > <https://github.com/stackforge/kolla/tree/master/docker/centos/binary/neutron> > > Note we are also in the process of adding build from source to our tree > here: > > > *https://github.com/stackforge/kolla/tree/master/docker/centos/source/neutron* > <https://github.com/stackforge/kolla/tree/master/docker/centos/source/neutron> > > For further background on Kolla, check out our wiki page: > > *https://wiki.openstack.org/wiki/Kolla* > <https://wiki.openstack.org/wiki/Kolla> > > Best wishes, > -steve > > *From: *Gal Sagie
Re: [openstack-dev] [Neutron][Kuryr][kolla] - Bringing Dockers networking to Neutron
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
regard.
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.
Best,
Mohammad
From: "Steven Dake (stdake)"
To: "OpenStack Development Mailing List (not for usage questions)"
, Eran Gampel
, Antoni Segura Puimedon
, Irena Berezovsky ,
"gal.sa...@gmail.com"
Date: 07/23/2015 11:34 AM
Subject: Re: [openstack-dev] [Neutron][Kuryr][kolla] - Bringing Dockers
networking to Neutron
Gal,
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
gerrit workflow.
https://github.com/stackforge/kolla/tree/master/docker/centos/binary/neutron
Note we are also in the process of adding build from source to our tree
here:
https://github.com/stackforge/kolla/tree/master/docker/centos/source/neutron
For further background on Kolla, check out our wiki page:
https://wiki.openstack.org/wiki/Kolla
Best wishes,
-steve
From: Gal Sagie
Reply-To: "OpenStack Development Mailing List (not for usage questions)" <
openstack-dev@lists.openstack.org>
Date: Wednesday, July 22, 2015 at 9:28 AM
To: "OpenStack Development Mailing List (not for usage questions)" <
openstack-dev@lists.openstack.org>, Eran Gampel <
eran.gam...@toganetworks.com>, Antoni Segura Puimedon ,
Irena Berezovsky
Subject: [openstack-dev] [Neutron][Kuryr] - Bringing Dockers networking to
Neutron
Hello Everyone,
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
time preference
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
everyone.
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
Thanks
Gal.
__
OpenStack Development Mailing List (not for usage questions)
Uns
Re: [openstack-dev] [Neutron][Kuryr][kolla] - Bringing Dockers networking to Neutron
Gal, 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 gerrit workflow. https://github.com/stackforge/kolla/tree/master/docker/centos/binary/neutron Note we are also in the process of adding build from source to our tree here: https://github.com/stackforge/kolla/tree/master/docker/centos/source/neutron For further background on Kolla, check out our wiki page: https://wiki.openstack.org/wiki/Kolla Best wishes, -steve From: Gal Sagie mailto:gal.sa...@gmail.com>> Reply-To: "OpenStack Development Mailing List (not for usage questions)" mailto:openstack-dev@lists.openstack.org>> Date: Wednesday, July 22, 2015 at 9:28 AM To: "OpenStack Development Mailing List (not for usage questions)" mailto:openstack-dev@lists.openstack.org>>, Eran Gampel mailto:eran.gam...@toganetworks.com>>, Antoni Segura Puimedon mailto:t...@midokura.com>>, Irena Berezovsky mailto:ir...@midokura.com>> Subject: [openstack-dev] [Neutron][Kuryr] - Bringing Dockers networking to Neutron Hello Everyone, 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 time preference 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 everyone. 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 Thanks Gal. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron][Kuryr][Kolla] - Bringing Dockers networking to Neutron
Thanks for bringing this to my attention Kevin! I may not have see this if my filter didn't catch 'Kolla'. I am very interested in this. In Kolla and related projects we containerize all the neutron components near the beginning of the year. We too have no wish to getting a situation where we are "re-inventing the wheel for each different project". Unfortunately, I am not seeing much documentation about this project. I would love to read more about the current status and plans so we can both contribute to each other! Sam Yaple On Wed, Jul 22, 2015 at 2:04 PM, Fox, Kevin M wrote: > Awesome. :) > > Dockerization of Neutron plugins is already in scope of the Kolla project. > Might want to coordinate the effort with the Kolla team. > > Thanks, > Kevin > > -- > *From:* Gal Sagie > *Sent:* Wednesday, July 22, 2015 9:28:50 AM > *To:* OpenStack Development Mailing List (not for usage questions); Eran > Gampel; Antoni Segura Puimedon; Irena Berezovsky > *Subject:* [openstack-dev] [Neutron][Kuryr] - Bringing Dockers networking > to Neutron > > > Hello Everyone, > > 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 time > preference > 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 > everyone. > > 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 > > Thanks > Gal. > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@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-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron][Kuryr][Kolla] - Bringing Dockers networking to Neutron
Awesome. :) Dockerization of Neutron plugins is already in scope of the Kolla project. Might want to coordinate the effort with the Kolla team. Thanks, Kevin From: Gal Sagie Sent: Wednesday, July 22, 2015 9:28:50 AM To: OpenStack Development Mailing List (not for usage questions); Eran Gampel; Antoni Segura Puimedon; Irena Berezovsky Subject: [openstack-dev] [Neutron][Kuryr] - Bringing Dockers networking to Neutron Hello Everyone, 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 time preference 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 everyone. 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 Thanks Gal. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
