Hi,
I would like to announce a new repository for tap-as-a-service was
created.
Could you please take a look.
http://git.openstack.org/cgit/openstack/tap-as-a-service-dashboard/
Regards,
Kaz
From: Akihiro Motoki
Subject: [openstack-dev] [neutron][horizon][fwaas][vpnaas] fwaas/vpnaas
First of all, IMHO this approach is not a requirement.
Each project can choose their preferred way.
# Hopefully all dashboards are listed in the horizon plugin registry
if you have a dashboard support.
# https://docs.openstack.org/developer/horizon/install/plugin-registry.html
The following is my
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 ho
Some context here:
http://lists.openstack.org/pipermail/openstack-dev/2017-April/115200.html
On Wed, Jun 21, 2017 at 2:33 AM, Thomas Morin
wrote:
> Hi Akihiro,
>
> While I understand the motivation to move these dashboards from
> openstack/horizon, what is the reason to prefer a distinct repo fo
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
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-vpnaas-dashboard/
All ne