<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On 12 December 2014 at 23:01, Yuriy Shovkoplias <span dir="ltr"><<a href="mailto:yshovkoplias@mirantis.com" target="_blank">yshovkoplias@mirantis.com</a>></span> wrote:<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr">Dear neutron community,<div><br></div><div>Can you please clarify couple points on the vendor code decomposition?</div><div> - Assuming I would like to create the new driver now (Kilo development cycle) - is it already allowed (or mandatory) to follow the new process?</div><div><blockquote style="margin:0px 0px 0px 40px;border:none;padding:0px"><div><a href="https://review.openstack.org/#/c/134680/" target="_blank">https://review.openstack.org/#/c/134680/</a></div></blockquote></div></div></blockquote><div><br></div><div>Yes. See [1] for more details.</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div><blockquote style="margin:0px 0px 0px 40px;border:none;padding:0px"><div><br></div></blockquote>- Assuming the new process is already in place, are the following guidelines still applicable for the vendor integration code (not for vendor library)?</div><div><blockquote style="margin:0px 0px 0px 40px;border:none;padding:0px"><div><a href="https://wiki.openstack.org/wiki/Neutron_Plugins_and_Drivers" target="_blank">https://wiki.openstack.org/wiki/Neutron_Plugins_and_Drivers</a><br></div><div><span style="color:rgb(51,51,51);font-family:'Arial Unicode MS',Arial,sans-serif;line-height:20px">The following is a list of requirements for inclusion of code upstream:</span><br></div><div><ul style="padding:0px;margin:0.3em 0px 0px 1.6em;color:rgb(51,51,51);line-height:20px"><li><font face="arial, helvetica, sans-serif">Participation in Neutron meetings, IRC channels, and email lists.</font></li><li><font face="arial, helvetica, sans-serif">A member of the plugin/driver team participating in code reviews of other upstream code.</font></li></ul></div></blockquote></div></div></blockquote><div><br></div><div>I see no reason why you wouldn't follow those guidelines, as a general rule of thumb. Having said that, some of the wording would need to be tweaked to take into account of the new contribution model. Bear in mind, that I started adding some developer documentation in [2], to give a practical guide to the proposal. More to follow.</div><div><br></div><div>Cheers,</div><div>Armando</div><div><br></div><div>[1] <a href="http://docs-draft.openstack.org/80/134680/17/check/gate-neutron-specs-docs/2a7afdd/doc/build/html/specs/kilo/core-vendor-decomposition.html#adoption-and-deprecation-policy">http://docs-draft.openstack.org/80/134680/17/check/gate-neutron-specs-docs/2a7afdd/doc/build/html/specs/kilo/core-vendor-decomposition.html#adoption-and-deprecation-policy</a><br></div><div>[2] <a href="https://review.openstack.org/#/q/status:open+project:openstack/neutron+branch:master+topic:bp/core-vendor-decomposition,n,z">https://review.openstack.org/#/q/status:open+project:openstack/neutron+branch:master+topic:bp/core-vendor-decomposition,n,z</a></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div>Regards,</div><div>Yuri</div><div><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Dec 11, 2014 at 3:23 AM, Gary Kotton <span dir="ltr"><<a href="mailto:gkotton@vmware.com" target="_blank">gkotton@vmware.com</a>></span> wrote:<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><br>
On 12/11/14, 12:50 PM, "Ihar Hrachyshka" <<a href="mailto:ihrachys@redhat.com" target="_blank">ihrachys@redhat.com</a>> wrote:<br>
<br>
>-----BEGIN PGP SIGNED MESSAGE-----<br>
>Hash: SHA512<br>
><br>
>+100. I vote -1 there and would like to point out that we *must* keep<br>
>history during the split, and split from u/s code base, not random<br>
>repositories. If you don't know how to achieve this, ask oslo people,<br>
>they did it plenty of times when graduating libraries from oslo-incubator.<br>
>/Ihar<br>
><br>
>On 10/12/14 19:18, Cedric OLLIVIER wrote:<br>
>> <<a href="https://review.openstack.org/#/c/140191/" target="_blank">https://review.openstack.org/#/c/140191/</a>><br>
>><br>
>> 2014-12-09 18:32 GMT+01:00 Armando M. <<a href="mailto:armamig@gmail.com" target="_blank">armamig@gmail.com</a><br>
>> <mailto:<a href="mailto:armamig@gmail.com" target="_blank">armamig@gmail.com</a>>>:<br>
>><br>
>><br>
>> By the way, if Kyle can do it in his teeny tiny time that he has<br>
>> left after his PTL duties, then anyone can do it! :)<br>
>><br>
>> <a href="https://review.openstack.org/#/c/140191/" target="_blank">https://review.openstack.org/#/c/140191/</a><br>
<br>
This patch looses the recent hacking changes that we have made. This is a<br>
slight example to try and highly the problem that we may incur as a<br>
community.<br>
<br>
>><br>
>> Fully cloning Dave Tucker's repository [1] and the outdated fork of<br>
>> the ODL ML2 MechanismDriver included raises some questions (e.g.<br>
>> [2]). I wish the next patch set removes some files. At least it<br>
>> should take the mainstream work into account (e.g. [3]) .<br>
>><br>
>> [1] <a href="https://github.com/dave-tucker/odl-neutron-drivers" target="_blank">https://github.com/dave-tucker/odl-neutron-drivers</a> [2]<br>
>> <a href="https://review.openstack.org/#/c/113330/" target="_blank">https://review.openstack.org/#/c/113330/</a> [3]<br>
>> <a href="https://review.openstack.org/#/c/96459/" target="_blank">https://review.openstack.org/#/c/96459/</a><br>
>><br>
>><br>
>> _______________________________________________ OpenStack-dev<br>
>> mailing list <a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</a><br>
>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
>><br>
>-----BEGIN PGP SIGNATURE-----<br>
>Version: GnuPG/MacGPG2 v2.0.22 (Darwin)<br>
><br>
>iQEcBAEBCgAGBQJUiXcIAAoJEC5aWaUY1u57dBMH/17unffokpb0uxqewPYrPNMI<br>
>ukDzG4dW8mIP3yfbVNsHQXe6gWj/kj/SkBWJrO13BusTu8hrr+DmOmmfF/42s3vY<br>
>E+6EppQDoUjR+QINBwE46nU+E1w9hIHyAZYbSBtaZQ32c8aQbmHmF+rgoeEQq349<br>
>PfpPLRI6MamFWRQMXSgF11VBTg8vbz21PXnN3KbHbUgzI/RS2SELv4SWmPgKZCEl<br>
>l1K5J1/Vnz2roJn4pr/cfc7vnUIeAB5a9AuBHC6o+6Je2RDy79n+oBodC27kmmIx<br>
>lVGdypoxZ9tF3yfRM9nngjkOtozNzZzaceH0Sc/5JR4uvNReVN4exzkX5fDH+SM=<br>
>=dfe/<br>
>-----END PGP SIGNATURE-----<br>
><br>
>_______________________________________________<br>
>OpenStack-dev mailing list<br>
><a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</a><br>
><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote></div><div><br></div>
</div></div></div></div>
<br>_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div></div></div>