Hi, > I think (a) is also good from TaaS dashboard.
This opinion is agreed as a TaaS project. Regards, Kaz From: "SUZUKI, Kazuhiro" <k...@jp.fujitsu.com> Subject: Re: [openstack-dev] [neutron][sfc][fwaas][taas][horizon] where would we like to have horizon dashboard for neutron stadium projects? Date: Wed, 12 Apr 2017 09:19:42 +0900 (JST) > Hi, > > I think (a) is also good from TaaS dashboard. > > Regards, > Kaz > > > From: Akihiro Motoki <amot...@gmail.com> > Subject: [openstack-dev] [neutron][sfc][fwaas][taas][horizon] where would we > like to have horizon dashboard for neutron stadium projects? > Date: Tue, 11 Apr 2017 00:09:10 +0900 > >> Hi neutrinos (and horizoners), >> >> As the title says, where would we like to have horizon dashboard for >> neutron stadium projects? >> There are several projects under neutron stadium and they are trying >> to add dashboard support. >> >> I would like to raise this topic again. No dashboard support lands since >> then. >> Also Horizon team would like to move in-tree neutron stadium dashboard >> (VPNaaS and FWaaS v1 dashboard) to outside of horizon repo. >> >> Possible approaches >> ---------------------------- >> >> Several possible options in my mind: >> (a) dashboard repository per project >> (b) dashboard code in individual project >> (c) a single dashboard repository for all neutron stadium projects >> >> Which one sounds better? >> >> Pros and Cons >> -------------------- >> >> (a) dashboard repository per project >> example, networking-sfc-dashboard repository for networking-sfc >> Pros >> - Can use existing horizon related project convention and knowledge >> (directory structure, testing, translation support) >> - Not related to the neutron stadium inclusion. Each project can >> provide its dashboard >> support regardless of neutron stadium inclusion. >> Cons >> - An additional repository is needed. >> >> (b) dashboard code in individual project >> example, dashboard module for networking-sfc >> Pros: >> - No additional repository >> - Not related to the neutron stadium inclusion. Each project can >> provide its dashboard >> support regardless of neutron stadium inclusion. >> Cons: >> - 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. >> >> (c) a single dashboard repository for all neutron stadium projects >> (something like neutron-advanced-dashboard) >> Pros: >> - No additional repository per project >> Each project do not need a basic setup for dashboard and >> possible makes things simple. >> Cons: >> - Inclusion criteria depending on the neutron stadium inclusion/exclusion >> (Similar discussion happens as for neutronclient OSC plugin) >> Project before neutron stadium inclusion may need another >> implementation. >> >> >> My vote is (a) or (c) (to avoid mixing neutron and dashboard codes in a >> repo). >> >> Note that as dashboard supports for feature in the main neutron repository >> are implemented in the horizon repository as we discussed several months ago. >> As an example, trunk support is being development in the horizon repo. >> >> Thanks, >> Akihiro >> >> __________________________________________________________________________ >> 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
