<div dir="ltr"><div>Folks - </div><div><br></div><div>I support the idea to keep plugins' code and other artifacts, e.g. design specs, installation and user guides, test scripts, test plan, test report, etc, in one repo, just to create dedicated folders for that.</div><div>My argument here is pretty simple, i consider a Fuel plugin as a separate and independent project, which should be stored in a dedicated repo and maintained by the plugin development team.</div><div><br></div><div>But i don't see why we can't use Fuel Launchpad [1] to create blueprints if we think it's necessary, but a BP itself shouldn't be a 'must do' for those who are working on Fuel plugins.</div><div><br></div><div>And couple more comments:<br></div><div><ol><li style="margin-left:15px"><span style="font-size:12.8000001907349px">Have a separate stackforge</span><span style="font-size:12.8000001907349px"> repo per Fuel plugin in format "fuel-plugin-<name>", with separate core-reviewers group which should have plugin contributor initially</span></li></ol><div><div>On stackforge.</div><div>Right now there are 4 Fuel plugins developed (GlusterFS, NetApp, LBaaS, VPNaaS) and 4 more are coming (NFS, FWaaS, Contrail, EMC VNX). Keeping in mind that the number of Fuel plugins will grow, does it make sense to keep them in stackforge?</div><div>Mike, Alexander, we discussed an option to keep everything in fuel-infra [3]. </div><div>I would like to hear what other folks think about that.</div></div><div><br></div><div>On the repo name.</div><div>I would suggest to add the name of OpenStack component the plugin works with also <span style="font-size:12.8000001907349px">"fuel-plugin-<component>-<name>", e.g. fuel-plugin-cinder-emc-vnx.</span></div><ol style="font-size:12.8000001907349px"><li style="margin-left:15px">Have docs folder in the plugin, and ability to build docs out of it</li><ul><li style="margin-left:15px">do we want Sphinx or simple Github docs format is Ok? So people can just go to github/stackforge to see docs</li></ul></ol><div><span style="font-size:12.8000001907349px">I agree with Evgeniy. We are talking about best practices of Fuel plugin development. I would prefer to keep them as simple and as easy as possible.</span></div><ol style="font-size:12.8000001907349px"><li style="margin-left:15px">Have specification in the plugin repo</li><ul><li style="margin-left:15px">also, do we need Sphinx here?</li></ul></ol><ol style="font-size:12.8000001907349px"><li style="margin-left:15px">Have plugins tests in the repo</li></ol><div><span style="font-size:12.8000001907349px">So, here is how the plugin repo structure could look like:</span></div></div><div><ul><li><span style="font-size:12.8000001907349px">fuel-plugin-<component>-</span><span style="font-size:12.8000001907349px"><name></span><br></li><ul><li><span style="font-size:12.8000001907349px">specs</span></li><li><span style="font-size:12.8000001907349px">plugin</span></li><li><span style="font-size:12.8000001907349px">tests</span></li><li><span style="font-size:12.8000001907349px">docs</span></li><li><span style="font-size:12.8000001907349px">utils</span></li></ul></ul></div><div>Alexander - </div><div><br></div><div>I don't think that putting these specs [4, 5] to fuel-specs [6] is a good idea.<br></div><div>Let's come to an agreement, so plugin developers will know where they should commit code,specs and other docs.</div><div><br></div><div>Looking forward to your comments.</div><div>Thanks.</div><div><br></div><div><br></div><div><span style="font-size:12.8000001907349px">[1] <a href="https://launchpad.net/fuel" target="_blank">https://launchpad.net/fuel</a></span></div><div><span style="font-size:12.8000001907349px">[2] <a href="https://github.com/stackforge" target="_blank">https://github.com/stackforge</a></span></div><div><span style="font-size:12.8000001907349px">[3] <a href="https://review.fuel-infra.org/" target="_blank">https://review.fuel-infra.org/</a></span></div><div><div style="font-size:12.8000001907349px">[4] <a href="https://review.openstack.org/#/c/129586/" target="_blank">https://review.openstack.org/#/c/129586/</a></div><div style="font-size:12.8000001907349px">[5] <a href="https://review.openstack.org/#/c/148475/4" target="_blank">https://review.openstack.org/#/c/148475/4</a></div></div><div><span style="font-size:12.8000001907349px">[6] <a href="https://github.com/stackforge/fuel-specs" target="_blank">https://github.com/stackforge/fuel-specs</a></span></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Jan 23, 2015 at 4:14 PM, Alexander Ignatov <span dir="ltr"><<a href="mailto:aignatov@mirantis.com" target="_blank">aignatov@mirantis.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div>Mike,</div><span class=""><div><br></div><div><blockquote type="cite">I also wanted to add that there is a PR already on adding plugins<br>repos to stackforge: <a href="https://review.openstack.org/#/c/147169/" target="_blank">https://review.openstack.org/#/c/147169/</a></blockquote></div></span><div>All this looks good, but it’s not clear when this patch will be merged and repos are created.</div><div>So the question is what should we do with the current spec made in fuel-specs[1,2] which are targeted for plugins?</div><div>And how will look development process for plugins added to 6.1 roadmap? </div><div>Especially for plugins came not from external vendors and partners. Will we create separate projects on the Launchpad and duplicate our </div><div>For now I’m not sure if we need to wait for new infrastructure created in stackforge/launchpad for each plugin and follow the common </div><div>procedure to land current plugins to existing repos during 6.1 milestone.</div><div><br></div><div>[1] <a href="https://review.openstack.org/#/c/129586/" target="_blank">https://review.openstack.org/#/c/129586/</a></div><div>[2] <a href="https://review.openstack.org/#/c/148475/4" target="_blank">https://review.openstack.org/#/c/148475/4</a></div><br><div>
<div>Regards,</div><div>Alexander Ignatov</div><div><br></div><br>
</div><div><div class="h5">
<br><div><blockquote type="cite"><div>On 23 Jan 2015, at 12:43, Nikolay Markov <<a href="mailto:nmarkov@mirantis.com" target="_blank">nmarkov@mirantis.com</a>> wrote:</div><br><div>I also wanted to add that there is a PR already on adding plugins<br>repos to stackforge: <a href="https://review.openstack.org/#/c/147169/" target="_blank">https://review.openstack.org/#/c/147169/</a><br><br>There is a battle in comments right now, because some people are not<br>agree that so many repos are needed.<br><br>On Fri, Jan 23, 2015 at 1:25 AM, Mike Scherbakov<br><<a href="mailto:mscherbakov@mirantis.com" target="_blank">mscherbakov@mirantis.com</a>> wrote:<br><blockquote type="cite">Hi Fuelers,<br>we've implemented pluggable architecture piece in 6.0, and got a number of<br>plugins already. Overall development process for plugins is still not fully<br>defined.<br>We initially thought that having all the plugins in one repo on stackforge<br>is Ok, we also put some docs into existing fuel-docs repo, and specs to<br>fuel-specs.<br><br>We might need a change here. Plugins are not tight to any particular release<br>date, and they can also be separated each from other in terms of committers<br>and core reviewers. Also, it seems to be pretty natural to keep all docs and<br>design specs associated with particular plugin.<br><br>With all said, following best dev practices, it is suggested to:<br><br>Have a separate stackforge repo per Fuel plugin in format<br>"fuel-plugin-<name>", with separate core-reviewers group which should have<br>plugin contributor initially<br>Have docs folder in the plugin, and ability to build docs out of it<br><br>do we want Sphinx or simple Github docs format is Ok? So people can just go<br>to github/stackforge to see docs<br><br>Have specification in the plugin repo<br><br>also, do we need Sphinx here?<br><br>Have plugins tests in the repo<br><br>Ideas / suggestions / comments?<br>Thanks,<br>--<br>Mike Scherbakov<br>#mihgen<br><br><br>__________________________________________________________________________<br>OpenStack Development Mailing List (not for usage questions)<br>Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org" target="_blank">OpenStack-dev-request@lists.openstack.org</a>?subject:unsubscribe<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><br><br><br>-- <br>Best regards,<br>Nick Markov<br><br>__________________________________________________________________________<br>OpenStack Development Mailing List (not for usage questions)<br>Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org" target="_blank">OpenStack-dev-request@lists.openstack.org</a>?subject:unsubscribe<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></blockquote></div><br></div></div></div><br>__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</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><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div>Regards,<br></div>Evgeniya Shumakher</div><div dir="ltr">Partner Integrations Manager <br><div>Mirantis, Inc</div><div><br></div><div><span style="color:rgb(34,34,34);background-color:rgb(255,255,255)">Mob.phone: +7 (968) 760-98-42</span><br style="color:rgb(34,34,34);background-color:rgb(255,255,255)"><span style="color:rgb(34,34,34);background-color:rgb(255,255,255)">Email: <a href="mailto:eshumakher@mirantis.com" target="_blank">eshumakher@mirantis.com</a></span><br style="color:rgb(34,34,34);background-color:rgb(255,255,255)"><span style="color:rgb(34,34,34);background-color:rgb(255,255,255)">Skype: eshumakher</span></div></div></div></div></div>
</div>