<html><body><p><tt>"Daneyon Hansen (danehans)" <danehans@cisco.com> wrote on 07/23/2015 03:40:38 PM:<br><br>> From: "Daneyon Hansen (danehans)" <danehans@cisco.com></tt><br><tt>> To: "OpenStack Development Mailing List (not for usage questions)" <br>> <openstack-dev@lists.openstack.org>, Mohammad Banikazemi/Watson/<br>> IBM@IBMUS, "Steven Dake (stdake)" <stdake@cisco.com></tt><br><tt>> Cc: Eran Gampel <Eran.Gampel@toganetworks.com>, Irena Berezovsky <br>> <irena@midokura.com></tt><br><tt>> Date: 07/23/2015 03:45 PM</tt><br><tt>> Subject: Re: [openstack-dev] [Neutron][Kuryr][kolla] - Bringing <br>> Dockers networking to Neutron</tt><br><tt>> <br>> From: Antoni Segura Puimedon <toni+openstackml@midokura.com><br>> Reply-To: "OpenStack Development Mailing List (not for usage questions)" <<br>> openstack-dev@lists.openstack.org><br>> Date: Thursday, July 23, 2015 at 11:16 AM<br>> To: Mohammad Banikazemi <mb@us.ibm.com>, "Steven Dake (stdake)" <<br>> stdake@cisco.com><br>> Cc: Eran Gampel <Eran.Gampel@toganetworks.com>, "OpenStack <br>> Development Mailing List (not for usage questions)" <openstack-<br>> dev@lists.openstack.org>, Irena Berezovsky <irena@midokura.com><br>> Subject: Re: [openstack-dev] [Neutron][Kuryr][kolla] - Bringing <br>> Dockers networking to Neutron</tt><br><tt>> <br>> Why is a separate OpenStack project needed to contribute to <br>> libnetwork? I would think the Neutron community would follow the <br>> libnetwork contrib guidelines and submit the code.</tt><br><tt>> <br></tt><br><tt>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.</tt><br><br><tt>Best,</tt><br><br><tt>Mohammad</tt><br><BR>
</body></html>