<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>Kevin Benton :<br>
> Some context here:
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/pipermail/openstack-dev/2017-April/115200.html">http://lists.openstack.org/pipermail/openstack-dev/2017-April/115200.html</a><br>
><br>
</p>
<p>Thanks, I had missed this one.</p>
<p>So, what I gather is that the only drawback noted for "(b)
dashboard code in individual project" is "Requires extra efforts
to support neutron and horizon codes in a single repository for
testing and translation supports. Each project needs to explore
the way.". While I won't disagree, my question would be the
following: since we have something that works (except dashboard
translation, which we haven't explored), should we move to the
model agreed on for new work (given that there is also overhead in
creating and maintaining a new repo) ?</p>
<p>Best,<br>
</p>
<p>-Thomas</p>
<p><br>
</p>
On Wed, Jun 21, 2017 at 2:33 AM, Thomas Morin <span dir="ltr"><<a
href="mailto:thomas.morin@orange.com" target="_blank"
moz-do-not-send="true">thomas.morin@orange.com</a>></span>
wrote:<br>
<blockquote type="cite"
cite="mid:CAO_F6JPwGw9SdV+TmKOc4KkS1e8pvFCnA=bN1XWszVarVGCdAg@mail.gmail.com">
<div class="gmail_extra">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<p>Hi Akihiro,</p>
<p><span class="m_-8129997830725823997js-navigation-open">While
I understand the motivation to move these dashboards
from openstack/horizon, what is the reason to prefer a
distinct repo for the dashboard rather than hosting it
in the main repo of these projects ?<br>
</span></p>
<p>(networking-bgpvpn has had a dashboard for some time
already, it is hosted under networking-bgpvpn/<span
class="m_-8129997830725823997js-navigation-open">bgpvpn_<wbr>dashboard
and we haven't heard about any drawback)<br>
</span></p>
<p><span class="m_-8129997830725823997js-navigation-open">Thanks,</span></p>
<p><span class="m_-8129997830725823997js-navigation-open">-Thomas<br>
</span></p>
<p><span class="m_-8129997830725823997js-navigation-open"><br>
</span></p>
<br>
<div class="m_-8129997830725823997moz-cite-prefix">Akihiro
Motoki :<br>
</div>
<div>
<div class="h5">
<blockquote type="cite">
<pre>Hi neutron and horizon teams (especially fwaas and vpnaas folks),
As we discussed so far, I prepared separate git repositories for FWaaS
and VPNaaS dashboards.
<a class="m_-8129997830725823997moz-txt-link-freetext" href="http://git.openstack.org/cgit/openstack/neutron-fwaas-dashboard/" target="_blank" moz-do-not-send="true">http://git.openstack.org/cgit/<wbr>openstack/neutron-fwaas-<wbr>dashboard/</a>
<a class="m_-8129997830725823997moz-txt-link-freetext" href="http://git.openstack.org/cgit/openstack/neutron-vpnaas-dashboard/" target="_blank" moz-do-not-send="true">http://git.openstack.org/cgit/<wbr>openstack/neutron-vpnaas-<wbr>dashboard/</a>
All new features will be implemented in the new repositories, for
example, FWaaS v2 support.
The initial core members consist of neutron-fwaas/vpnaas-core
(respectively) + horizon-core.
There are several things to do to complete the split out.
I gathered a list of work items at the etherpad and we will track the
progress here.
<a class="m_-8129997830725823997moz-txt-link-freetext" href="https://etherpad.openstack.org/p/horizon-fwaas-vpnaas-splitout" target="_blank" moz-do-not-send="true">https://etherpad.openstack.<wbr>org/p/horizon-fwaas-vpnaas-<wbr>splitout</a>
If you are interested in helping the efforts, sign up on the etherpad
or contact me.
I would like to release the initial release which is compatible with
the current horizon
FWaaS/VPNaaS dashboard (with no new features).
I hope we can release it around R-8 week (Jul 3) or R-7 (Jul 10).
It also will be good examples for neutron stadium/related projects
which are interested in
adding dashboard support. AFAIK, networking-sfc, tap-as-a-service are
interested in it.
Thanks,
Akihiro
______________________________<wbr>______________________________<wbr>______________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: <a class="m_-8129997830725823997moz-txt-link-abbreviated" href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank" moz-do-not-send="true">OpenStack-dev-request@lists.<wbr>openstack.org?subject:<wbr>unsubscribe</a>
<a class="m_-8129997830725823997moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank" moz-do-not-send="true">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a>
</pre>
</blockquote>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
</div>
</div>
</div>
<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" moz-do-not-send="true">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" moz-do-not-send="true">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><br>
<br>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: <a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
</blockquote>
<br>
</body>
</html>