Re: [openstack-dev] [Horizon][Neutron] dashboard repository for neutron subprojects

[Ihar Hrachyshka]

Akihiro Motoki  wrote:


[Packaging perspective]

I am not sure how it affects.
There is one concern as a package consumer.

Getting additional packages through distro channels can be surprisingly  
difficult for new packages. :/


How neutron team can answer to this?
I think it is not specific to neutron subproject dashboard discussion.
Neutron stadium mode already has this problem.
Input from packaging side would be appreciated.


Distributions should work on fixing their processes. That’s what RDO  
project is going through right now (f.e. we got rid of Fedora package  
review process [that usually took too much time] as a prerequisite step for  
inclusion). But if you still feel issues with proposing a new package for  
RDO for neutron bits, please talk to me.


Ihar

__
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

Re: [openstack-dev] [Horizon][Neutron] dashboard repository for neutron subprojects

[Fawad Khaliq]

On Wed, Dec 23, 2015 at 9:16 PM, Akihiro Motoki  wrote:

> Are there no comment after I added more detail?
> No inputs from both horizon and neutron side.
>
> Although Horizon team is tackling to address some problems around
> horizon plugin mechanism
> such as translations, I think option (c) requires neutron subprojects
> to do some extra efforts
> around infra scripts. They are specific to neutron subproject
> directory structure and neutron
> subprojects should be responsible to deal with them as option (c) is a
> choice of neutron side.
> please check the details of my previous post.
>
> I am not sure it is okay to neutron suboprojects?
>
I think option (c) would work fine. My vote would be to go with it. Would
be best if someone could capture a devref around this similar to what
HenryG did around DB and alembic for subprojects.

>
> Akihiro
>
>
> 2015-12-02 17:23 GMT+09:00 Akihiro Motoki :
> > Thanks all.
> > All comments so far are from neutron side. I would like to wait inputs
> > from horizon side, especially David.
> >
> > Option (c) is what we do in neutron sub-projects under neutron stadium
> model and
> > I agree it makes sense and sounds natural to neutron folks.
> >
> > My initial mail just did not cover technical points or horizon
> > developer perspective
> > if we go to option (c). Let me share them.
> >
> > [Horizon developer perspective]
> >
> > I think we need some collaboration points between neutron subprojects
> > and horizon team (+ UX team).
> > to share knowledge or conventions in the dashboard development.
> > Not so many neutron developers are aware of horizon side changes, so I
> > think Horizon side
> > needs to care of these repositories to some extent for better UX
> > consistency or framework changes.
> >
> > We are going to the self-management models in individual repos, so I
> believe
> > each team watches horizon side changes to some extent, and keep their
> > dashboard up-to-date.
> >
> > From Horizon point of view, it seems good to me if the following are
> done:
> >
> > - Use a consistent directory name for a dashboard support in each
> > repository (e.g., "dashboard")
> >   Gerrit support filename based query, so it allows horizon developers
> > can reach dashboard related reviews.
> > - Keep up-to-date Horizon plugin registry
> > http://docs.openstack.org/developer/horizon/plugins.html
> > - Use horizon plugin model rather than adhoc approach
> > - Documentation on config options (at now, horizon does not support
> > oslo.config generator)
> >
> > [Technical topics]
> >
> > - We need to have two testing setup for both neutron and horizon.
> >   I think most dashboard tests depend on Horizon (or at least Django)
> >
> > - Does (test-)requirements.txt contain neutron and horizon dependencies?
> >   For horizon itself, perhaps no. Our test tool chains should install
> horizon
> >   as we do for neutron dependency.
> >   For other requirements, I am not sure at this moment.
> >
> > - Separate translation support for dashboard and server code.
> >   Django and oslo.i18n (python gettext) use different approach to find
> > translation catalog,
> >   so we need to prepare a separate tool chain for both translation
> catalog.
> >   It requires the infra script change.
> >
> >   # Normal Horizon plugin translation support is an ongoing effort,
> >   # but option (c) needs extra effort.
> >
> > [Packaging perspective]
> >
> > I am not sure how it affects.
> > There is one concern as a package consumer.
> >
> >> Getting additional packages through distro channels can be surprisingly
> difficult for new packages. :/
> >
> > How neutron team can answer to this?
> > I think it is not specific to neutron subproject dashboard discussion.
> > Neutron stadium mode already has this problem.
> > Input from packaging side would be appreciated.
> >
> > Thanks,
> > Akihiro
> >
> > 2015-11-25 14:46 GMT+09:00 Akihiro Motoki :
> >> Hi,
> >>
> >> Neutron has now various subprojects and some of them would like to
> >> implement Horizon supports. Most of them are additional features.
> >> I would like to start the discussion where we should have horizon
> support.
> >>
> >> [Background]
> >> Horizon team introduced a plugin mechanism and we can add horizon panels
> >> from external repositories. Horizon team is recommending external repos
> for
> >> additional services for faster iteration and features.
> >> We have various horizon related repositories now [1].
> >>
> >> In Neutron related world, we have neutron-lbaas-dashboard and
> >> horizon-cisco-ui repos.
> >>
> >> [Possible options]
> >> There are several possible options for neutron sub-projects.
> >> My current vote is (b), and the next is (a). It looks a good balance to
> me.
> >> I would like to gather broader opinions,
> >>
> >> (a) horizon in-tree repo
> >> - [+] It was a legacy approach and there is no initial effort to setup
> a repo.
> >> - [+] Easy to share code 

Re: [openstack-dev] [Horizon][Neutron] dashboard repository for neutron subprojects

[Akihiro Motoki]

Thanks all.
All comments so far are from neutron side. I would like to wait inputs
from horizon side, especially David.

Option (c) is what we do in neutron sub-projects under neutron stadium model and
I agree it makes sense and sounds natural to neutron folks.

My initial mail just did not cover technical points or horizon
developer perspective
if we go to option (c). Let me share them.

[Horizon developer perspective]

I think we need some collaboration points between neutron subprojects
and horizon team (+ UX team).
to share knowledge or conventions in the dashboard development.
Not so many neutron developers are aware of horizon side changes, so I
think Horizon side
needs to care of these repositories to some extent for better UX
consistency or framework changes.

We are going to the self-management models in individual repos, so I believe
each team watches horizon side changes to some extent, and keep their
dashboard up-to-date.

>From Horizon point of view, it seems good to me if the following are done:

- Use a consistent directory name for a dashboard support in each
repository (e.g., "dashboard")
  Gerrit support filename based query, so it allows horizon developers
can reach dashboard related reviews.
- Keep up-to-date Horizon plugin registry
http://docs.openstack.org/developer/horizon/plugins.html
- Use horizon plugin model rather than adhoc approach
- Documentation on config options (at now, horizon does not support
oslo.config generator)

[Technical topics]

- We need to have two testing setup for both neutron and horizon.
  I think most dashboard tests depend on Horizon (or at least Django)

- Does (test-)requirements.txt contain neutron and horizon dependencies?
  For horizon itself, perhaps no. Our test tool chains should install horizon
  as we do for neutron dependency.
  For other requirements, I am not sure at this moment.

- Separate translation support for dashboard and server code.
  Django and oslo.i18n (python gettext) use different approach to find
translation catalog,
  so we need to prepare a separate tool chain for both translation catalog.
  It requires the infra script change.

  # Normal Horizon plugin translation support is an ongoing effort,
  # but option (c) needs extra effort.

[Packaging perspective]

I am not sure how it affects.
There is one concern as a package consumer.

> Getting additional packages through distro channels can be surprisingly 
> difficult for new packages. :/

How neutron team can answer to this?
I think it is not specific to neutron subproject dashboard discussion.
Neutron stadium mode already has this problem.
Input from packaging side would be appreciated.

Thanks,
Akihiro

2015-11-25 14:46 GMT+09:00 Akihiro Motoki :
> Hi,
>
> Neutron has now various subprojects and some of them would like to
> implement Horizon supports. Most of them are additional features.
> I would like to start the discussion where we should have horizon support.
>
> [Background]
> Horizon team introduced a plugin mechanism and we can add horizon panels
> from external repositories. Horizon team is recommending external repos for
> additional services for faster iteration and features.
> We have various horizon related repositories now [1].
>
> In Neutron related world, we have neutron-lbaas-dashboard and
> horizon-cisco-ui repos.
>
> [Possible options]
> There are several possible options for neutron sub-projects.
> My current vote is (b), and the next is (a). It looks a good balance to me.
> I would like to gather broader opinions,
>
> (a) horizon in-tree repo
> - [+] It was a legacy approach and there is no initial effort to setup a repo.
> - [+] Easy to share code conventions.
> - [-] it does not scale. Horizon team can be a bottleneck.
>
> (b) a single dashboard repo for all neutron sub-projects
> - [+] No need to set up a repo by each sub-project
> - [+] Easier to share the code convention. Can get horizon reviewers.
> - [-] who will be a core reviewer of this repo?
>
> (c) neutron sub-project repo
> - [+] Each sub-project can develop a dashboard fast.
> - [-] It is doable, but the directory tree can be complicated.
> - [-] Lead to too many repos and the horizon team/liaison cannot cover all.
>
> (d) a separate repo per neutron sub-project
> Similar to (c)
> - [+] A dedicate repo for dashboard simplifies the directory tree.
> - [-] Need to setup a separate repo.
> - [-] Lead to too many repos and the horizon team/liaison cannot cover all.
>
>
> Note that this mail is not intended to move the current neutron
> support in horizon
> to outside of horizon tree. I would like to discuss Horizon support of
> additional features.
>
> Akihiro
>
> [1] http://docs.openstack.org/developer/horizon/plugins.html

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

Re: [openstack-dev] [Horizon][Neutron] dashboard repository for neutron subprojects

[Brandon Logan]

Sent from Nine<http://www.9folders.com/>

From: Kyle Mestery <mest...@mestery.com>
Sent: Nov 25, 2015 8:18 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Horizon][Neutron] dashboard repository for 
neutron subprojects

On Wed, Nov 25, 2015 at 1:06 AM, Armando M. 
<arma...@gmail.com<mailto:arma...@gmail.com>> wrote:


On 24 November 2015 at 21:46, Akihiro Motoki 
<amot...@gmail.com<mailto:amot...@gmail.com>> wrote:
Hi,

Neutron has now various subprojects and some of them would like to
implement Horizon supports. Most of them are additional features.
I would like to start the discussion where we should have horizon support.

[Background]
Horizon team introduced a plugin mechanism and we can add horizon panels
from external repositories. Horizon team is recommending external repos for
additional services for faster iteration and features.
We have various horizon related repositories now [1].

In Neutron related world, we have neutron-lbaas-dashboard and
horizon-cisco-ui repos.

[Possible options]
There are several possible options for neutron sub-projects.
My current vote is (b), and the next is (a). It looks a good balance to me.
I would like to gather broader opinions,

(a) horizon in-tree repo
- [+] It was a legacy approach and there is no initial effort to setup a repo.
- [+] Easy to share code conventions.
- [-] it does not scale. Horizon team can be a bottleneck.

(b) a single dashboard repo for all neutron sub-projects
- [+] No need to set up a repo by each sub-project
- [+] Easier to share the code convention. Can get horizon reviewers.
- [-] who will be a core reviewer of this repo?

(c) neutron sub-project repo

All circumstances considered, I think c) is the only viable one.

+1

- [+] Each sub-project can develop a dashboard fast.
- [-] It is doable, but the directory tree can be complicated.

why? do you envision something else other than /horizon directory in the tree?

- [-] Lead to too many repos and the horizon team/liaison cannot cover all.

If that's true for horizon, shouldn't the same be true for the neutron team :)? 
IMO, the level of feedback/oversight provided is always going to be constant 
(you can't clone people) no matter how the efforts are distributed. I'd rather 
empower the individual projects.

+1000

Option C seems like the way forward here.


(d) a separate repo per neutron sub-project
Similar to (c)
- [+] A dedicate repo for dashboard simplifies the directory tree.
- [-] Need to setup a separate repo.
- [-] Lead to too many repos and the horizon team/liaison cannot cover all.

Note that this mail is not intended to move the current neutron
support in horizon
to outside of horizon tree. I would like to discuss Horizon support of
additional features.

Akihiro

[1] http://docs.openstack.org/developer/horizon/plugins.html

__
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


__
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


 I have to agree with C) as well.  I do worry about the scope of the projects 
becoming way too large though.  If this continues these projects are going to 
need to have people that are SMEs in all things OR implement something like the 
Lt system main neutron has right now.  I'm OK crossing that bridge when we get 
to it though.
__
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

Re: [openstack-dev] [Horizon][Neutron] dashboard repository for neutron subprojects

[Cathy Zhang]

 I have some questions on option (c) and would like to make sure we are on the 
same page.

Thanks,
Cathy


(c) neutron sub-project repo
- [+] Each sub-project can develop a dashboard fast.
- [-] It is doable, but the directory tree can be complicated.
- [-] Lead to too many repos and the horizon team/liaison cannot cover all.
If we work in the same mode as we do DevStack plugins today, that is inside the 
sub-projects repo, the number of repos should be equal to the number of 
sub-projects. Also, this simplifies the packaging and allow each subproject 
owners to take ownership of the code. Guidance from Horizon folks will be 
appreciated to help the interested people get started. Question is: does 
Horizon plugin follow the same model as Neutron plugins like all the code is 
part of Horizon umbrella? If yes, then this might not be the ideal option.

Cathy> Thanks Akihiro for starting this discussion. +1 for the idea of doing 
this within each sub-project repo since its functionality is closely associated 
with the other code patches of the sub-project. Networking-sfc has already 
developed a Horizon dashboard in Horizon tree, but we got suggestion from 
Horizon team to move the code to the separate project repo. We are interested 
in trying this approach in the network-sfc project. Since this is a new way to 
add Horizon plugin, we would like to get guidance from Horizon folks. Is 
Horizon folks OK for this option and will give each Neutron sub-project the 
needed support? I think  Fawad raised a good question here. Does the Horizon 
code in each Neutron sub-project repo a part of Horizon umbrella? Do we need to 
get Horizon team’s approval for the code merge? If so, it comes back to the 
issue of how we can ensure faster iteration?



(d) a separate repo per neutron sub-project
Similar to (c)
- [+] A dedicate repo for dashboard simplifies the directory tree.
- [-] Need to setup a separate repo.
- [-] Lead to too many repos and the horizon team/liaison cannot cover all.
 Agree


Note that this mail is not intended to move the current neutron
support in horizon
to outside of horizon tree. I would like to discuss Horizon support of
additional features.

Akihiro

[1] http://docs.openstack.org/developer/horizon/plugins.html

__
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

Re: [openstack-dev] [Horizon][Neutron] dashboard repository for neutron subprojects

[Fox, Kevin M]

Getting additional packages through distro channels can be surprisingly 
difficult for new packages. :/

So having one new package for neutron-subprojects-dashboard rather then many 
might be much easier.

Thanks,
Kevin 

From: Akihiro Motoki [amot...@gmail.com]
Sent: Tuesday, November 24, 2015 9:46 PM
To: OpenStack Development Mailing List
Subject: [openstack-dev] [Horizon][Neutron] dashboard repository for neutron
subprojects

Hi,

Neutron has now various subprojects and some of them would like to
implement Horizon supports. Most of them are additional features.
I would like to start the discussion where we should have horizon support.

[Background]
Horizon team introduced a plugin mechanism and we can add horizon panels
from external repositories. Horizon team is recommending external repos for
additional services for faster iteration and features.
We have various horizon related repositories now [1].

In Neutron related world, we have neutron-lbaas-dashboard and
horizon-cisco-ui repos.

[Possible options]
There are several possible options for neutron sub-projects.
My current vote is (b), and the next is (a). It looks a good balance to me.
I would like to gather broader opinions,

(a) horizon in-tree repo
- [+] It was a legacy approach and there is no initial effort to setup a repo.
- [+] Easy to share code conventions.
- [-] it does not scale. Horizon team can be a bottleneck.

(b) a single dashboard repo for all neutron sub-projects
- [+] No need to set up a repo by each sub-project
- [+] Easier to share the code convention. Can get horizon reviewers.
- [-] who will be a core reviewer of this repo?

(c) neutron sub-project repo
- [+] Each sub-project can develop a dashboard fast.
- [-] It is doable, but the directory tree can be complicated.
- [-] Lead to too many repos and the horizon team/liaison cannot cover all.

(d) a separate repo per neutron sub-project
Similar to (c)
- [+] A dedicate repo for dashboard simplifies the directory tree.
- [-] Need to setup a separate repo.
- [-] Lead to too many repos and the horizon team/liaison cannot cover all.


Note that this mail is not intended to move the current neutron
support in horizon
to outside of horizon tree. I would like to discuss Horizon support of
additional features.

Akihiro

[1] http://docs.openstack.org/developer/horizon/plugins.html

__
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

Re: [openstack-dev] [Horizon][Neutron] dashboard repository for neutron subprojects

[Paul Michali]

I like the idea of doing a Horizon plugin, similar to a devstack plugin...
So choice (c) is my preference, given my current understanding. May be good
to try it on one subproject and see how it works out. Would give a concrete
example to discuss.

Regards,

Paul Michali (pc_m)

On Wed, Nov 25, 2015 at 2:13 AM Fawad Khaliq  wrote:

> On Wed, Nov 25, 2015 at 12:06 PM, Armando M.  wrote:
>
>>
>>
>> On 24 November 2015 at 21:46, Akihiro Motoki  wrote:
>>
>>> Hi,
>>>
>>> Neutron has now various subprojects and some of them would like to
>>> implement Horizon supports. Most of them are additional features.
>>> I would like to start the discussion where we should have horizon
>>> support.
>>>
>>> [Background]
>>> Horizon team introduced a plugin mechanism and we can add horizon panels
>>> from external repositories. Horizon team is recommending external repos
>>> for
>>> additional services for faster iteration and features.
>>> We have various horizon related repositories now [1].
>>>
>>> In Neutron related world, we have neutron-lbaas-dashboard and
>>> horizon-cisco-ui repos.
>>>
>>> [Possible options]
>>> There are several possible options for neutron sub-projects.
>>> My current vote is (b), and the next is (a). It looks a good balance to
>>> me.
>>> I would like to gather broader opinions,
>>>
>>> (a) horizon in-tree repo
>>> - [+] It was a legacy approach and there is no initial effort to setup a
>>> repo.
>>> - [+] Easy to share code conventions.
>>> - [-] it does not scale. Horizon team can be a bottleneck.
>>>
>>> (b) a single dashboard repo for all neutron sub-projects
>>> - [+] No need to set up a repo by each sub-project
>>> - [+] Easier to share the code convention. Can get horizon reviewers.
>>> - [-] who will be a core reviewer of this repo?
>>>
>>> (c) neutron sub-project repo
>>>
>>
>> All circumstances considered, I think c) is the only viable one.
>>
> +1
>
>>
>>
>>> - [+] Each sub-project can develop a dashboard fast.
>>> - [-] It is doable, but the directory tree can be complicated.
>>>
>>
>> why? do you envision something else other than /horizon directory in the
>> tree?
>>
>>
>>> - [-] Lead to too many repos and the horizon team/liaison cannot cover
>>> all.
>>>
>>
>> If that's true for horizon, shouldn't the same be true for the neutron
>> team :)? IMO, the level of feedback/oversight provided is always going to
>> be constant (you can't clone people) no matter how the efforts are
>> distributed. I'd rather empower the individual projects.
>>
> Agree. +1
>
>>
>>
>>>
>>> (d) a separate repo per neutron sub-project
>>> Similar to (c)
>>> - [+] A dedicate repo for dashboard simplifies the directory tree.
>>> - [-] Need to setup a separate repo.
>>> - [-] Lead to too many repos and the horizon team/liaison cannot cover
>>> all.
>>>
>>
>>> Note that this mail is not intended to move the current neutron
>>> support in horizon
>>> to outside of horizon tree. I would like to discuss Horizon support of
>>> additional features.
>>>
>>> Akihiro
>>>
>>> [1] http://docs.openstack.org/developer/horizon/plugins.html
>>>
>>>
>>> __
>>> 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
>>
>> __
> 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

Re: [openstack-dev] [Horizon][Neutron] dashboard repository for neutron subprojects

[Kyle Mestery]

On Wed, Nov 25, 2015 at 1:06 AM, Armando M.  wrote:

>
>
> On 24 November 2015 at 21:46, Akihiro Motoki  wrote:
>
>> Hi,
>>
>> Neutron has now various subprojects and some of them would like to
>> implement Horizon supports. Most of them are additional features.
>> I would like to start the discussion where we should have horizon support.
>>
>> [Background]
>> Horizon team introduced a plugin mechanism and we can add horizon panels
>> from external repositories. Horizon team is recommending external repos
>> for
>> additional services for faster iteration and features.
>> We have various horizon related repositories now [1].
>>
>> In Neutron related world, we have neutron-lbaas-dashboard and
>> horizon-cisco-ui repos.
>>
>> [Possible options]
>> There are several possible options for neutron sub-projects.
>> My current vote is (b), and the next is (a). It looks a good balance to
>> me.
>> I would like to gather broader opinions,
>>
>> (a) horizon in-tree repo
>> - [+] It was a legacy approach and there is no initial effort to setup a
>> repo.
>> - [+] Easy to share code conventions.
>> - [-] it does not scale. Horizon team can be a bottleneck.
>>
>> (b) a single dashboard repo for all neutron sub-projects
>> - [+] No need to set up a repo by each sub-project
>> - [+] Easier to share the code convention. Can get horizon reviewers.
>> - [-] who will be a core reviewer of this repo?
>>
>> (c) neutron sub-project repo
>>
>
> All circumstances considered, I think c) is the only viable one.
>
>
+1


> - [+] Each sub-project can develop a dashboard fast.
>> - [-] It is doable, but the directory tree can be complicated.
>>
>
> why? do you envision something else other than /horizon directory in the
> tree?
>
>
>> - [-] Lead to too many repos and the horizon team/liaison cannot cover
>> all.
>>
>
> If that's true for horizon, shouldn't the same be true for the neutron
> team :)? IMO, the level of feedback/oversight provided is always going to
> be constant (you can't clone people) no matter how the efforts are
> distributed. I'd rather empower the individual projects.
>
>
+1000

Option C seems like the way forward here.


>
>> (d) a separate repo per neutron sub-project
>> Similar to (c)
>> - [+] A dedicate repo for dashboard simplifies the directory tree.
>> - [-] Need to setup a separate repo.
>> - [-] Lead to too many repos and the horizon team/liaison cannot cover
>> all.
>>
>
>> Note that this mail is not intended to move the current neutron
>> support in horizon
>> to outside of horizon tree. I would like to discuss Horizon support of
>> additional features.
>>
>> Akihiro
>>
>> [1] http://docs.openstack.org/developer/horizon/plugins.html
>>
>> __
>> 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
>
>
__
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

Re: [openstack-dev] [Horizon][Neutron] dashboard repository for neutron subprojects

[Fawad Khaliq]

Hi Akihiro,

Great initiative.

On Wed, Nov 25, 2015 at 10:46 AM, Akihiro Motoki  wrote:

> Hi,
>
> Neutron has now various subprojects and some of them would like to
> implement Horizon supports. Most of them are additional features.
> I would like to start the discussion where we should have horizon support.
>
> [Background]
> Horizon team introduced a plugin mechanism and we can add horizon panels
> from external repositories. Horizon team is recommending external repos for
> additional services for faster iteration and features.
> We have various horizon related repositories now [1].
>
> In Neutron related world, we have neutron-lbaas-dashboard and
> horizon-cisco-ui repos.
>
> [Possible options]
> There are several possible options for neutron sub-projects.
> My current vote is (b), and the next is (a). It looks a good balance to me.
> I would like to gather broader opinions,
>
> (a) horizon in-tree repo
> - [+] It was a legacy approach and there is no initial effort to setup a
> repo.
> - [+] Easy to share code conventions.
> - [-] it does not scale. Horizon team can be a bottleneck.

Based on the learnings from Neutron plugins, it makes sense not to go down
this route.

>
> (b) a single dashboard repo for all neutron sub-projects
> - [+] No need to set up a repo by each sub-project
> - [+] Easier to share the code convention. Can get horizon reviewers.
> - [-] who will be a core reviewer of this repo?

Over here, for sub-project specific Horizon features, we will be adding
complexity of packaging/configuration.


>
> (c) neutron sub-project repo
> - [+] Each sub-project can develop a dashboard fast.
> - [-] It is doable, but the directory tree can be complicated.
> - [-] Lead to too many repos and the horizon team/liaison cannot cover all.
>
If we work in the same mode as we do DevStack plugins today, that is inside
the sub-projects repo, the number of repos should be equal to the number of
sub-projects. Also, this simplifies the packaging and allow each subproject
owners to take ownership of the code. Guidance from Horizon folks will be
appreciated to help the interested people get started. Question is: does
Horizon plugin follow the same model as Neutron plugins like all the code
is part of Horizon umbrella? If yes, then this might not be the ideal
option.


>
> (d) a separate repo per neutron sub-project
> Similar to (c)
> - [+] A dedicate repo for dashboard simplifies the directory tree.
> - [-] Need to setup a separate repo.
> - [-] Lead to too many repos and the horizon team/liaison cannot cover all.

 Agree

>
>
> Note that this mail is not intended to move the current neutron
> support in horizon
> to outside of horizon tree. I would like to discuss Horizon support of
> additional features.
>
> Akihiro
>
> [1] http://docs.openstack.org/developer/horizon/plugins.html
>
> __
> 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

Re: [openstack-dev] [Horizon][Neutron] dashboard repository for neutron subprojects

[Armando M.]

On 24 November 2015 at 21:46, Akihiro Motoki  wrote:

> Hi,
>
> Neutron has now various subprojects and some of them would like to
> implement Horizon supports. Most of them are additional features.
> I would like to start the discussion where we should have horizon support.
>
> [Background]
> Horizon team introduced a plugin mechanism and we can add horizon panels
> from external repositories. Horizon team is recommending external repos for
> additional services for faster iteration and features.
> We have various horizon related repositories now [1].
>
> In Neutron related world, we have neutron-lbaas-dashboard and
> horizon-cisco-ui repos.
>
> [Possible options]
> There are several possible options for neutron sub-projects.
> My current vote is (b), and the next is (a). It looks a good balance to me.
> I would like to gather broader opinions,
>
> (a) horizon in-tree repo
> - [+] It was a legacy approach and there is no initial effort to setup a
> repo.
> - [+] Easy to share code conventions.
> - [-] it does not scale. Horizon team can be a bottleneck.
>
> (b) a single dashboard repo for all neutron sub-projects
> - [+] No need to set up a repo by each sub-project
> - [+] Easier to share the code convention. Can get horizon reviewers.
> - [-] who will be a core reviewer of this repo?
>
> (c) neutron sub-project repo
>

All circumstances considered, I think c) is the only viable one.


> - [+] Each sub-project can develop a dashboard fast.
> - [-] It is doable, but the directory tree can be complicated.
>

why? do you envision something else other than /horizon directory in the
tree?


> - [-] Lead to too many repos and the horizon team/liaison cannot cover all.
>

If that's true for horizon, shouldn't the same be true for the neutron team
:)? IMO, the level of feedback/oversight provided is always going to be
constant (you can't clone people) no matter how the efforts are
distributed. I'd rather empower the individual projects.


>
> (d) a separate repo per neutron sub-project
> Similar to (c)
> - [+] A dedicate repo for dashboard simplifies the directory tree.
> - [-] Need to setup a separate repo.
> - [-] Lead to too many repos and the horizon team/liaison cannot cover
> all.
>

> Note that this mail is not intended to move the current neutron
> support in horizon
> to outside of horizon tree. I would like to discuss Horizon support of
> additional features.
>
> Akihiro
>
> [1] http://docs.openstack.org/developer/horizon/plugins.html
>
> __
> 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

Re: [openstack-dev] [Horizon][Neutron] dashboard repository for neutron subprojects

[Fawad Khaliq]

On Wed, Nov 25, 2015 at 12:06 PM, Armando M.  wrote:

>
>
> On 24 November 2015 at 21:46, Akihiro Motoki  wrote:
>
>> Hi,
>>
>> Neutron has now various subprojects and some of them would like to
>> implement Horizon supports. Most of them are additional features.
>> I would like to start the discussion where we should have horizon support.
>>
>> [Background]
>> Horizon team introduced a plugin mechanism and we can add horizon panels
>> from external repositories. Horizon team is recommending external repos
>> for
>> additional services for faster iteration and features.
>> We have various horizon related repositories now [1].
>>
>> In Neutron related world, we have neutron-lbaas-dashboard and
>> horizon-cisco-ui repos.
>>
>> [Possible options]
>> There are several possible options for neutron sub-projects.
>> My current vote is (b), and the next is (a). It looks a good balance to
>> me.
>> I would like to gather broader opinions,
>>
>> (a) horizon in-tree repo
>> - [+] It was a legacy approach and there is no initial effort to setup a
>> repo.
>> - [+] Easy to share code conventions.
>> - [-] it does not scale. Horizon team can be a bottleneck.
>>
>> (b) a single dashboard repo for all neutron sub-projects
>> - [+] No need to set up a repo by each sub-project
>> - [+] Easier to share the code convention. Can get horizon reviewers.
>> - [-] who will be a core reviewer of this repo?
>>
>> (c) neutron sub-project repo
>>
>
> All circumstances considered, I think c) is the only viable one.
>
+1

>
>
>> - [+] Each sub-project can develop a dashboard fast.
>> - [-] It is doable, but the directory tree can be complicated.
>>
>
> why? do you envision something else other than /horizon directory in the
> tree?
>
>
>> - [-] Lead to too many repos and the horizon team/liaison cannot cover
>> all.
>>
>
> If that's true for horizon, shouldn't the same be true for the neutron
> team :)? IMO, the level of feedback/oversight provided is always going to
> be constant (you can't clone people) no matter how the efforts are
> distributed. I'd rather empower the individual projects.
>
Agree. +1

>
>
>>
>> (d) a separate repo per neutron sub-project
>> Similar to (c)
>> - [+] A dedicate repo for dashboard simplifies the directory tree.
>> - [-] Need to setup a separate repo.
>> - [-] Lead to too many repos and the horizon team/liaison cannot cover
>> all.
>>
>
>> Note that this mail is not intended to move the current neutron
>> support in horizon
>> to outside of horizon tree. I would like to discuss Horizon support of
>> additional features.
>>
>> Akihiro
>>
>> [1] http://docs.openstack.org/developer/horizon/plugins.html
>>
>> __
>> 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
>
>
__
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