<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<div>Hi All:</div>
<div><br>
</div>
<div>From and FWaaS perspective – we also think (a) would be ideal.</div>
<div><br>
</div>
<div>Thanks</div>
<div><br>
</div>
<div>Sridar</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>Kevin Benton <<a href="mailto:kevin@benton.pub">kevin@benton.pub</a>><br>
<span style="font-weight:bold">Reply-To: </span>OpenStack List <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
<span style="font-weight:bold">Date: </span>Monday, April 10, 2017 at 4:20 PM<br>
<span style="font-weight:bold">To: </span>OpenStack List <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
<span style="font-weight:bold">Subject: </span>Re: [openstack-dev] [neutron][sfc][fwaas][taas][horizon] where would we like to have horizon dashboard for neutron stadium projects?<br>
</div>
<div><br>
</div>
<div>
<div>
<div dir="auto">I think 'a' is probably the way to go since we can mainly rely on existing horizon guides for creating new dashboard repos. </div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Apr 10, 2017 08:11, "Akihiro Motoki" <<a href="mailto:amotoki@gmail.com">amotoki@gmail.com</a>> wrote:<br type="attribution">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
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>
______________________________<wbr>______________________________<wbr>______________<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.<wbr>openstack.org?subject:<wbr>unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><br>
</blockquote>
</div>
</div>
</div>
</div>
</span>
</body>
</html>