<div dir="ltr">><span style="font-family:arial,sans-serif;font-size:13.333333015441895px">I also feel like the drivers/plugins are currently BEYOND a tipping</span><br style="font-family:arial,sans-serif;font-size:13.333333015441895px">
<span style="font-family:arial,sans-serif;font-size:13.333333015441895px">point, and are in fact dragging down velocity of the core project in</span><br style="font-family:arial,sans-serif;font-size:13.333333015441895px">
<span style="font-family:arial,sans-serif;font-size:13.333333015441895px">many ways.</span><div><span style="font-family:arial,sans-serif;font-size:13.333333015441895px"><br></span></div><div><span style="font-family:arial,sans-serif;font-size:13.333333015441895px">Can you elaborate on the ways that they are slowing down the velocity? I know they take up reviewer time, but are there other ways that you think they slow down the project?</span></div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Aug 14, 2014 at 6:07 AM, Kyle Mestery <span dir="ltr"><<a href="mailto:mestery@mestery.com" target="_blank">mestery@mestery.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I also feel like the drivers/plugins are currently BEYOND a tipping<br>
point, and are in fact dragging down velocity of the core project in<br>
many ways. I'm working on a proposal for Kilo where we move all<br>
drivers/plugins out of the main Neutron tree and into a separate git<br>
repository under the networking program. We have way too many drivers,<br>
requiring way too man review cycles, for this to be a sustainable<br>
model going forward. Since the main reason plugin/driver authors want<br>
their code upstream is to be a part of the simultaneous release, and<br>
thus be packaged by distributions, having a separate repository for<br>
these will satisfy this requirement. I'm still working through the<br>
details around reviews of this repository, etc.<br>
<br>
Also, I feel as if the level of passion on the mailing list has died<br>
down a bit, so I thought I'd send something out to try and liven<br>
things up a bit. It's been somewhat non-emotional here for a day or<br>
so. :)<br>
<br>
Thanks,<br>
Kyle<br>
<div class="HOEnZb"><div class="h5"><br>
On Thu, Aug 14, 2014 at 5:09 AM, Salvatore Orlando <<a href="mailto:sorlando@nicira.com">sorlando@nicira.com</a>> wrote:<br>
> I think there will soon be a discussion regarding what the appropriate<br>
> location for plugin and drivers should be.<br>
> My personal feeling is that Neutron has simply reached the tipping point<br>
> where the high number of drivers and plugins is causing unnecessary load for<br>
> the core team and frustration for the community.<br>
><br>
> There I would totally support Luke's initiative about maintaining an<br>
> out-of-tree ML2 driver. On the other hand, a plugin/driver "diaspora" might<br>
> also have negative consequences such as frequent breakages such as those Bob<br>
> was mentioning or confusion for users which might need to end up fetching<br>
> drivers from disparate sources.<br>
><br>
> As mentioned during the last Neutron IRC meeting this is another "process"<br>
> aspect which will be discussed soon, with the aim of defining a plan for:<br>
> - drastically reduce the number of plugins and drivers which must be<br>
> maintained in the main source tree<br>
> - enhance control of plugin/driver maintainers over their own code<br>
> - preserve the ability of doing CI checks on gerrit as we do today<br>
> - raise the CI bar (maybe finally set the smoketest as a minimum<br>
> requirement?)<br>
><br>
> Regards,<br>
> Salvatore<br>
><br>
><br>
><br>
> On 14 August 2014 11:47, loy wolfe <<a href="mailto:loywolfe@gmail.com">loywolfe@gmail.com</a>> wrote:<br>
>><br>
>><br>
>><br>
>><br>
>> On Thu, Aug 14, 2014 at 4:22 PM, Mathieu Rohon <<a href="mailto:mathieu.rohon@gmail.com">mathieu.rohon@gmail.com</a>><br>
>> wrote:<br>
>>><br>
>>> Hi,<br>
>>><br>
>>> I would like to add that it would be harder for the community to help<br>
>>> maintaining drivers.<br>
>>> such a work [1] wouldn't have occured with an out of tree ODL driver.<br>
>><br>
>><br>
>> +1.<br>
>> It's better to move all MD for none built-in backend out of tree,<br>
>> maintaining these drivers shouldn't be the responsibility of community. Not<br>
>> only MD, but also plugin, agent should all obey this rule<br>
>><br>
>>><br>
>>><br>
>>> [1] <a href="https://review.openstack.org/#/c/96459/" target="_blank">https://review.openstack.org/#/c/96459/</a><br>
>>><br>
>>> On Wed, Aug 13, 2014 at 1:09 PM, Robert Kukura <<a href="mailto:kukura@noironetworks.com">kukura@noironetworks.com</a>><br>
>>> wrote:<br>
>>> > One thing to keep in mind is that the ML2 driver API does sometimes<br>
>>> > change,<br>
>>> > requiring updates to drivers. Drivers that are in-tree get updated<br>
>>> > along<br>
>>> > with the driver API change. Drivers that are out-of-tree must be<br>
>>> > updated by<br>
>>> > the owner.<br>
>>> ><br>
>>> > -Bob<br>
>>> ><br>
>>> ><br>
>>> > On 8/13/14, 6:59 AM, ZZelle wrote:<br>
>>> ><br>
>>> > Hi,<br>
>>> ><br>
>>> ><br>
>>> > The important thing to understand is how to integrate with neutron<br>
>>> > through<br>
>>> > stevedore/entrypoints:<br>
>>> ><br>
>>> ><br>
>>> > <a href="https://github.com/dave-tucker/odl-neutron-drivers/blob/master/setup.cfg#L32-L34" target="_blank">https://github.com/dave-tucker/odl-neutron-drivers/blob/master/setup.cfg#L32-L34</a><br>
>>> ><br>
>>> ><br>
>>> > Cedric<br>
>>> ><br>
>>> ><br>
>>> > On Wed, Aug 13, 2014 at 12:17 PM, Dave Tucker <<a href="mailto:dave@dtucker.co.uk">dave@dtucker.co.uk</a>><br>
>>> > wrote:<br>
>>> >><br>
>>> >> I've been working on this for OpenDaylight<br>
>>> >> <a href="https://github.com/dave-tucker/odl-neutron-drivers" target="_blank">https://github.com/dave-tucker/odl-neutron-drivers</a><br>
>>> >><br>
>>> >> This seems to work for me (tested Devstack w/ML2) but YMMV.<br>
>>> >><br>
>>> >> -- Dave<br>
>>> >><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>
>>> ><br>
>>> ><br>
>>> ><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>
>>> ><br>
>>> ><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>
>>><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>
>><br>
>><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>
><br>
><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>
<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>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div>Kevin Benton</div>
</div>