[openstack-dev] [Neutron] Core/Vendor code decomposition

Yuriy Shovkoplias yshovkoplias at mirantis.com
Sat Dec 13 07:01:31 UTC 2014


Dear neutron community,

Can you please clarify couple points on the vendor code decomposition?
 - Assuming I would like to create the new driver now (Kilo development
cycle) - is it already allowed (or mandatory) to follow the new process?

https://review.openstack.org/#/c/134680/

- Assuming the new process is already in place, are the following
guidelines still applicable for the vendor integration code (not for vendor
library)?

https://wiki.openstack.org/wiki/Neutron_Plugins_and_Drivers
The following is a list of requirements for inclusion of code upstream:

   - Participation in Neutron meetings, IRC channels, and email lists.
   - A member of the plugin/driver team participating in code reviews of
   other upstream code.

Regards,
Yuri

On Thu, Dec 11, 2014 at 3:23 AM, Gary Kotton <gkotton at vmware.com> wrote:
>
>
> On 12/11/14, 12:50 PM, "Ihar Hrachyshka" <ihrachys at redhat.com> wrote:
>
> >-----BEGIN PGP SIGNED MESSAGE-----
> >Hash: SHA512
> >
> >+100. I vote -1 there and would like to point out that we *must* keep
> >history during the split, and split from u/s code base, not random
> >repositories. If you don't know how to achieve this, ask oslo people,
> >they did it plenty of times when graduating libraries from oslo-incubator.
> >/Ihar
> >
> >On 10/12/14 19:18, Cedric OLLIVIER wrote:
> >> <https://review.openstack.org/#/c/140191/>
> >>
> >> 2014-12-09 18:32 GMT+01:00 Armando M. <armamig at gmail.com
> >> <mailto:armamig at gmail.com>>:
> >>
> >>
> >> By the way, if Kyle can do it in his teeny tiny time that he has
> >> left after his PTL duties, then anyone can do it! :)
> >>
> >> https://review.openstack.org/#/c/140191/
>
> This patch looses the recent hacking changes that we have made. This is a
> slight example to try and highly the problem that we may incur as a
> community.
>
> >>
> >> Fully cloning Dave Tucker's repository [1] and the outdated fork of
> >> the ODL ML2 MechanismDriver included raises some questions (e.g.
> >> [2]). I wish the next patch set removes some files. At least it
> >> should take the mainstream work into account (e.g. [3]) .
> >>
> >> [1] https://github.com/dave-tucker/odl-neutron-drivers [2]
> >> https://review.openstack.org/#/c/113330/ [3]
> >> https://review.openstack.org/#/c/96459/
> >>
> >>
> >> _______________________________________________ OpenStack-dev
> >> mailing list OpenStack-dev at lists.openstack.org
> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >>
> >-----BEGIN PGP SIGNATURE-----
> >Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
> >
> >iQEcBAEBCgAGBQJUiXcIAAoJEC5aWaUY1u57dBMH/17unffokpb0uxqewPYrPNMI
> >ukDzG4dW8mIP3yfbVNsHQXe6gWj/kj/SkBWJrO13BusTu8hrr+DmOmmfF/42s3vY
> >E+6EppQDoUjR+QINBwE46nU+E1w9hIHyAZYbSBtaZQ32c8aQbmHmF+rgoeEQq349
> >PfpPLRI6MamFWRQMXSgF11VBTg8vbz21PXnN3KbHbUgzI/RS2SELv4SWmPgKZCEl
> >l1K5J1/Vnz2roJn4pr/cfc7vnUIeAB5a9AuBHC6o+6Je2RDy79n+oBodC27kmmIx
> >lVGdypoxZ9tF3yfRM9nngjkOtozNzZzaceH0Sc/5JR4uvNReVN4exzkX5fDH+SM=
> >=dfe/
> >-----END PGP SIGNATURE-----
> >
> >_______________________________________________
> >OpenStack-dev mailing list
> >OpenStack-dev at lists.openstack.org
> >http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20141212/560f7d9f/attachment.html>


More information about the OpenStack-dev mailing list