Kevin Benton :
> Some context here:
http://lists.openstack.org/pipermail/openstack-dev/2017-April/115200.html
>
Thanks, I had missed this one.
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) ?
Best,
-Thomas
On Wed, Jun 21, 2017 at 2:33 AM, Thomas Morin <thomas.mo...@orange.com
<mailto:thomas.mo...@orange.com>> wrote:
Hi Akihiro,
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 ?
(networking-bgpvpn has had a dashboard for some time already, it
is hosted under networking-bgpvpn/bgpvpn_dashboard and we haven't
heard about any drawback)
Thanks,
-Thomas
Akihiro Motoki :
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.
http://git.openstack.org/cgit/openstack/neutron-fwaas-dashboard/
<http://git.openstack.org/cgit/openstack/neutron-fwaas-dashboard/>
http://git.openstack.org/cgit/openstack/neutron-vpnaas-dashboard/
<http://git.openstack.org/cgit/openstack/neutron-vpnaas-dashboard/>
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.
https://etherpad.openstack.org/p/horizon-fwaas-vpnaas-splitout
<https://etherpad.openstack.org/p/horizon-fwaas-vpnaas-splitout>
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
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
<mailto:openstack-dev-requ...@lists.openstack.org?subject:unsubscribe>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
<http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev>
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
<http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
<http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev>
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
