<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Title" content="">
<meta name="Keywords" content="">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:Calibri;
color:windowtext;}
span.msoIns
{mso-style-type:export-only;
mso-style-name:"";
text-decoration:underline;
color:teal;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:595.0pt 842.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body bgcolor="white" lang="EN-GB" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri;mso-fareast-language:EN-US">Are there any implications for the end user experience by going to different repos (such as requiring dedicated menu items)?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri;mso-fareast-language:EN-US">Tim<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal" style="margin-left:36.0pt"><b><span style="font-family:Calibri;color:black">From:
</span></b><span style="font-family:Calibri;color:black">"Sridar Kandaswamy (skandasw)" <skandasw@cisco.com><br>
<b>Reply-To: </b>"OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org><br>
<b>Date: </b>Tuesday, 11 April 2017 at 17:01<br>
<b>To: </b>"OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org><br>
<b>Subject: </b>Re: [openstack-dev] [neutron][sfc][fwaas][taas][horizon] where would we like to have horizon dashboard for neutron stadium projects?<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt">Hi All:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt">From and FWaaS perspective – we also think (a) would be ideal.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt">Thanks<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt">Sridar<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><o:p> </o:p></p>
</div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal" style="margin-left:36.0pt"><b><span style="font-size:11.0pt;font-family:Calibri;color:black">From:
</span></b><span style="font-size:11.0pt;font-family:Calibri;color:black">Kevin Benton <<a href="mailto:kevin@benton.pub">kevin@benton.pub</a>><br>
<b>Reply-To: </b>OpenStack List <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
<b>Date: </b>Monday, April 10, 2017 at 4:20 PM<br>
<b>To: </b>OpenStack List <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
<b>Subject: </b>Re: [openstack-dev] [neutron][sfc][fwaas][taas][horizon] where would we like to have horizon dashboard for neutron stadium projects?<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><o:p> </o:p></p>
</div>
<div>
<div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt">I think 'a' is probably the way to go since we can mainly rely on existing horizon guides for creating new dashboard repos. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><o:p> </o:p></p>
<div>
<p class="MsoNormal" style="margin-left:36.0pt">On Apr 10, 2017 08:11, "Akihiro Motoki" <<a href="mailto:amotoki@gmail.com">amotoki@gmail.com</a>> wrote:<o:p></o:p></p>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<p class="MsoNormal" style="margin-left:36.0pt">Hi neutrinos (and horizoners),<br>
<br>
As the title says, where would we like to have horizon dashboard for<br>
neutron stadium projects?<br>
There are several projects under neutron stadium and they are trying<br>
to add dashboard support.<br>
<br>
I would like to raise this topic again. No dashboard support lands since then.<br>
Also Horizon team would like to move in-tree neutron stadium dashboard<br>
(VPNaaS and FWaaS v1 dashboard) to outside of horizon repo.<br>
<br>
Possible approaches<br>
----------------------------<br>
<br>
Several possible options in my mind:<br>
(a) dashboard repository per project<br>
(b) dashboard code in individual project<br>
(c) a single dashboard repository for all neutron stadium projects<br>
<br>
Which one sounds better?<br>
<br>
Pros and Cons<br>
--------------------<br>
<br>
(a) dashboard repository per project<br>
example, networking-sfc-dashboard repository for networking-sfc<br>
Pros<br>
- Can use existing horizon related project convention and knowledge<br>
(directory structure, testing, translation support)<br>
- Not related to the neutron stadium inclusion. Each project can<br>
provide its dashboard<br>
support regardless of neutron stadium inclusion.<br>
Cons<br>
- An additional repository is needed.<br>
<br>
(b) dashboard code in individual project<br>
example, dashboard module for networking-sfc<br>
Pros:<br>
- No additional repository<br>
- Not related to the neutron stadium inclusion. Each project can<br>
provide its dashboard<br>
support regardless of neutron stadium inclusion.<br>
Cons:<br>
- Requires extra efforts to support neutron and horizon codes in a<br>
single repository<br>
for testing and translation supports. Each project needs to<br>
explore the way.<br>
<br>
(c) a single dashboard repository for all neutron stadium projects<br>
(something like neutron-advanced-dashboard)<br>
Pros:<br>
- No additional repository per project<br>
Each project do not need a basic setup for dashboard and<br>
possible makes things simple.<br>
Cons:<br>
- Inclusion criteria depending on the neutron stadium inclusion/exclusion<br>
(Similar discussion happens as for neutronclient OSC plugin)<br>
Project before neutron stadium inclusion may need another implementation.<br>
<br>
<br>
My vote is (a) or (c) (to avoid mixing neutron and dashboard codes in a repo).<br>
<br>
Note that as dashboard supports for feature in the main neutron repository<br>
are implemented in the horizon repository as we discussed several months ago.<br>
As an example, trunk support is being development in the horizon repo.<br>
<br>
Thanks,<br>
Akihiro<br>
<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><o:p></o:p></p>
</blockquote>
</div>
</div>
</div>
</div>
</div>
</body>
</html>