settingsLogin | Registersettings

[openstack-dev] [neutron][sfc][fwaas][taas][horizon] where would we like to have horizon dashboard for neutron stadium projects?

0 votes

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-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
asked Apr 11, 2017 in openstack-dev by Akihiro_Motoki (8,520 points)   2 3 4

9 Responses

0 votes

Excerpts from Akihiro Motoki's message of 2017-04-11 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

From the release team's perspective, we would prefer (a), because
having one deliverable per package simplifies packaging and makes
more sense for deployments (no one would end up with dashboard
panels for features not supported by the backend).

Doug


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded Apr 10, 2017 by Doug_Hellmann (87,520 points)   3 4 9
0 votes

I think 'a' is probably the way to go since we can mainly rely on existing
horizon guides for creating new dashboard repos.

On Apr 10, 2017 08:11, "Akihiro Motoki" amotoki@gmail.com wrote:

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-request@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-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded Apr 10, 2017 by kevin_at_benton.pub (15,600 points)   2 3 4
0 votes

Hi All:

From and FWaaS perspective - we also think (a) would be ideal.

Thanks

Sridar

From: Kevin Benton kevin@benton.pub
Reply-To: OpenStack List openstack-dev@lists.openstack.org
Date: Monday, April 10, 2017 at 4:20 PM
To: OpenStack List openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [neutron][sfc][fwaas][taas][horizon] where would we like to have horizon dashboard for neutron stadium projects?

I think 'a' is probably the way to go since we can mainly rely on existing horizon guides for creating new dashboard repos.

On Apr 10, 2017 08:11, "Akihiro Motoki" amotoki@gmail.com wrote:
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-request@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-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded Apr 11, 2017 by Sridar_Kandaswamy_(s (1,000 points)   1
0 votes

Akihiro,
Option (a) would have my vote.
- Louis

-----Original Message-----
From: Akihiro Motoki [mailto:amotoki@gmail.com]
Sent: Monday, April 10, 2017 8:09 AM
To: OpenStack Development Mailing List
Subject: [openstack-dev] [neutron][sfc][fwaas][taas][horizon] where would we like to have horizon dashboard for neutron stadium projects?

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-request@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-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded Apr 11, 2017 by Henry_Fourie (1,720 points)   2
0 votes

Are there any implications for the end user experience by going to different repos (such as requiring dedicated menu items)?

Tim

From: "Sridar Kandaswamy (skandasw)" skandasw@cisco.com
Reply-To: "OpenStack Development Mailing List (not for usage questions)" openstack-dev@lists.openstack.org
Date: Tuesday, 11 April 2017 at 17:01
To: "OpenStack Development Mailing List (not for usage questions)" openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [neutron][sfc][fwaas][taas][horizon] where would we like to have horizon dashboard for neutron stadium projects?

Hi All:

From and FWaaS perspective – we also think (a) would be ideal.

Thanks

Sridar

From: Kevin Benton kevin@benton.pub
Reply-To: OpenStack List openstack-dev@lists.openstack.org
Date: Monday, April 10, 2017 at 4:20 PM
To: OpenStack List openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [neutron][sfc][fwaas][taas][horizon] where would we like to have horizon dashboard for neutron stadium projects?

I think 'a' is probably the way to go since we can mainly rely on existing horizon guides for creating new dashboard repos.

On Apr 10, 2017 08:11, "Akihiro Motoki" amotoki@gmail.com wrote:
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-request@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-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded Apr 11, 2017 by Tim_Bell (16,440 points)   1 6 10
0 votes

Hi,

I think (a) is also good from TaaS dashboard.

Regards,
Kaz

From: Akihiro Motoki amotoki@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-request@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-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded Apr 12, 2017 by SUZUKI,_Kazuhiro (540 points)  
0 votes

Hi,

I think (a) is also good from TaaS dashboard.

This opinion is agreed as a TaaS project.

Regards,
Kaz

From: "SUZUKI, Kazuhiro" kaz@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 amotoki@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-request@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-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded Apr 12, 2017 by SUZUKI,_Kazuhiro (540 points)  
0 votes

Hi TIm,

I think no user-visible changes happen for users.
Do you have any example in your mind?

I understand horizon lacks supports of some hooks (such as adding a
menu to an existing table).
If there are missing things,

2017-04-12 2:24 GMT+09:00 Tim Bell Tim.Bell@cern.ch:

Are there any implications for the end user experience by going to different
repos (such as requiring dedicated menu items)?

Tim

From: "Sridar Kandaswamy (skandasw)" skandasw@cisco.com
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
openstack-dev@lists.openstack.org
Date: Tuesday, 11 April 2017 at 17:01
To: "OpenStack Development Mailing List (not for usage questions)"
openstack-dev@lists.openstack.org

Subject: Re: [openstack-dev] [neutron][sfc][fwaas][taas][horizon] where
would we like to have horizon dashboard for neutron stadium projects?

Hi All:

From and FWaaS perspective – we also think (a) would be ideal.

Thanks

Sridar

From: Kevin Benton kevin@benton.pub
Reply-To: OpenStack List openstack-dev@lists.openstack.org
Date: Monday, April 10, 2017 at 4:20 PM
To: OpenStack List openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [neutron][sfc][fwaas][taas][horizon] where
would we like to have horizon dashboard for neutron stadium projects?

I think 'a' is probably the way to go since we can mainly rely on existing
horizon guides for creating new dashboard repos.

On Apr 10, 2017 08:11, "Akihiro Motoki" amotoki@gmail.com wrote:

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-request@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-request@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-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded Apr 17, 2017 by Akihiro_Motoki (8,520 points)   2 3 4
0 votes

Thanks for your feedback, all!
It seems we have a consensus and the route is "(a) dashboard
repository per project".
I would suggest xxxx-dashboard as a repository name where xxxx is your
main repo name.

2017-04-11 0:09 GMT+09:00 Akihiro Motoki amotoki@gmail.com:

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-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded Apr 18, 2017 by Akihiro_Motoki (8,520 points)   2 3 4
...