<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
<div style="font-family:Calibri, Arial, Helvetica, sans-serif; font-size:12.0pt; color:#1F497D">
<div><br>
</div>
<div><br>
</div>
<div id="signature-x" style="-webkit-user-select:none; font-family:Calibri, Arial, Helvetica, sans-serif; font-size:12.0pt; color:#1F497D">
Sent from <a href="http://www.9folders.com/" style="text-decoration:none;color:#009BDF">
Nine</a></div>
</div>
<div id="quoted_header" style="clear:both;"><br>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<span style="font-size:11.0pt;font-family:Calibri, Arial, Helvetica, sans-serif"><b>From:</b> Kyle Mestery <mestery@mestery.com><br>
<b>Sent:</b> Nov 25, 2015 8:18 AM<br>
<b>To:</b> OpenStack Development Mailing List (not for usage questions)<br>
<b>Subject:</b> Re: [openstack-dev] [Horizon][Neutron] dashboard repository for neutron subprojects<br>
</span></div>
</div>
<br type="attribution">
<div id="quoted_body">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">On Wed, Nov 25, 2015 at 1:06 AM, Armando M. <span dir="ltr">
<<a href="mailto:armamig@gmail.com">armamig@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex; border-left:1px #ccc solid; padding-left:1ex">
<div dir="ltr"><br>
<div class="gmail_extra"><br>
<div class="gmail_quote">
<div>
<div class="h5">On 24 November 2015 at 21:46, Akihiro Motoki <span dir="ltr"><<a href="mailto:amotoki@gmail.com">amotoki@gmail.com</a>></span> wrote:<br>
<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">
Hi,<br>
<br>
Neutron has now various subprojects and some of them would like to<br>
implement Horizon supports. Most of them are additional features.<br>
I would like to start the discussion where we should have horizon support.<br>
<br>
[Background]<br>
Horizon team introduced a plugin mechanism and we can add horizon panels<br>
from external repositories. Horizon team is recommending external repos for<br>
additional services for faster iteration and features.<br>
We have various horizon related repositories now [1].<br>
<br>
In Neutron related world, we have neutron-lbaas-dashboard and<br>
horizon-cisco-ui repos.<br>
<br>
[Possible options]<br>
There are several possible options for neutron sub-projects.<br>
My current vote is (b), and the next is (a). It looks a good balance to me.<br>
I would like to gather broader opinions,<br>
<br>
(a) horizon in-tree repo<br>
- [+] It was a legacy approach and there is no initial effort to setup a repo.<br>
- [+] Easy to share code conventions.<br>
- [-] it does not scale. Horizon team can be a bottleneck.<br>
<br>
(b) a single dashboard repo for all neutron sub-projects<br>
- [+] No need to set up a repo by each sub-project<br>
- [+] Easier to share the code convention. Can get horizon reviewers.<br>
- [-] who will be a core reviewer of this repo?<br>
<br>
(c) neutron sub-project repo<br>
</blockquote>
<br>
</div>
</div>
<div>All circumstances considered, I think c) is the only viable one.</div>
<span class="">
<div> </div>
</span></div>
</div>
</div>
</blockquote>
<div>+1<br>
<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex; border-left:1px #ccc solid; padding-left:1ex">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote"><span class="">
<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">
- [+] Each sub-project can develop a dashboard fast.<br>
- [-] It is doable, but the directory tree can be complicated.<br>
</blockquote>
<div><br>
</div>
</span>
<div>why? do you envision something else other than /horizon directory in the tree?</div>
<span class="">
<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">
- [-] Lead to too many repos and the horizon team/liaison cannot cover all.<br>
</blockquote>
<div><br>
</div>
</span>
<div>If that's true for horizon, shouldn't the same be true for the neutron team :)? IMO, the level of feedback/oversight provided is always going to be constant (you can't clone people) no matter how the efforts are distributed. I'd rather empower the individual
projects.</div>
<span class="">
<div> </div>
</span></div>
</div>
</div>
</blockquote>
<div>+1000<br>
<br>
</div>
<div>Option C seems like the way forward here.<br>
<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex; border-left:1px #ccc solid; padding-left:1ex">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote"><span class="">
<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>
(d) a separate repo per neutron sub-project<br>
Similar to (c)<br>
- [+] A dedicate repo for dashboard simplifies the directory tree.<br>
- [-] Need to setup a separate repo.<br>
- [-] Lead to too many repos and the horizon team/liaison cannot cover all. <br>
</blockquote>
<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>
Note that this mail is not intended to move the current neutron<br>
support in horizon<br>
to outside of horizon tree. I would like to discuss Horizon support of<br>
additional features.<br>
<br>
Akihiro<br>
<br>
[1] <a href="http://docs.openstack.org/developer/horizon/plugins.html" rel="noreferrer" target="_BLANK">
http://docs.openstack.org/developer/horizon/plugins.html</a><br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_BLANK">
OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_BLANK">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote>
</span></div>
<br>
</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" rel="noreferrer" target="_BLANK">
OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_BLANK">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br>
</blockquote>
</div>
<br>
</div>
<div class="gmail_extra"><span style="font-family: sans-serif;"> I have to agree with C) as well. I do worry about the scope of the projects becoming way too large though. If this continues these projects are going to need to have people that are SMEs in
all things OR implement something like the Lt system main neutron has right now. I'm OK crossing that bridge when we get to it though.</span><br>
</div>
</div>
</div>
</body>
</html>