"Daneyon Hansen (danehans)" <[email protected]> wrote on 07/23/2015 03:40:38 PM: > From: "Daneyon Hansen (danehans)" <[email protected]> > To: "OpenStack Development Mailing List (not for usage questions)" > <[email protected]>, Mohammad Banikazemi/Watson/ > IBM@IBMUS, "Steven Dake (stdake)" <[email protected]> > Cc: Eran Gampel <[email protected]>, Irena Berezovsky > <[email protected]> > Date: 07/23/2015 03:45 PM > Subject: Re: [openstack-dev] [Neutron][Kuryr][kolla] - Bringing > Dockers networking to Neutron > > From: Antoni Segura Puimedon <[email protected]> > Reply-To: "OpenStack Development Mailing List (not for usage questions)" < > [email protected]> > Date: Thursday, July 23, 2015 at 11:16 AM > To: Mohammad Banikazemi <[email protected]>, "Steven Dake (stdake)" < > [email protected]> > Cc: Eran Gampel <[email protected]>, "OpenStack > Development Mailing List (not for usage questions)" <openstack- > [email protected]>, Irena Berezovsky <[email protected]> > 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: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
