Open Stack

On Sat, Dec 3, 2016 at 4:35 AM, Ken'ichi Ohmichi <ken1ohmichi at gmail.com>
wrote:

> 2016-12-02 5:39 GMT-08:00 Masayuki Igawa <masayuki at igawa.me>:
> > Hi,
> >
> > On Fri, Dec 2, 2016 at 6:29 PM, Andreas Jaeger <aj at suse.com> wrote:
> >> On 12/02/2016 10:03 AM, Thierry Carrez wrote:
> >>> Ken'ichi Ohmichi wrote:
> >>>> Hi QA-team,
> >>>>
> >>>> In the big-tent policy, we continue creating new projects.
> >>>> On the other hand, some projects became non-active.
> >>>> That seems natural thing.
> >>>>
> >>>> Now openstack-health[1] shows non-active project as 100% failure ratio
> >>>> on "Project Status".
> >>>> The project has became non-official since
> >>>>
> ​​
> https://review.openstack.org/#/c/324412/
> >>>> So I feel it is nice to have black-list or something to make it
> >>>> disappear from the dashboard for concentrating on active projects'
> >>>> failures.
> >>>>
> >>>> Any thoughts?
> >>>
> >>> Yes, I totally agree we should only list active official projects in
> >>> there, otherwise long-dead things like Cue will make the view look bad.
> >>> Looks like the system adds new ones but does not remove anything ? It
> >>> should probably take its list from [1].
> >>>
> >>> [1]
> >>> http://git.openstack.org/cgit/openstack/governance/tree/
> reference/projects.yaml
> >>
> >> Is cue completely dead? Should we then retire it completely following
> >> http://docs.openstack.org/infra/manual/drivers.html#retiring-a-project
> ?
> >>
> >> It still has jobs setup and I see people submitting typo fixes etc.
> >
> > I'm not sure the cue is dead or not. But I think we should fix the
> > failure of the job or remove the periodic jobs. Otherwise, the job
> > just waste the resource of the OpenStack infra..
>
> Yeah, that is a nice point.
> And this case means openstack-health notifies this wasting resource on
> the infra, that is good thing.
> The failing job is already removed since
> https://review.openstack.org/#/c/404375/
> So we will not see the failure on the dashboard soon, thanks for helping
> that.
>
>
​Completely agree on removal of non active one.

Failure status from o-h is nice input for removal the inactive projects
from OpenStack. So once it is removed from governance then we can remove
from o-h too.​
​For non-official one, we can just remove based on their failure frequency
etc. ​



> > But we should have the filter feature like a 'Project Type' of
> > stackalitics, probably. I think it's useful for openstack-health
> > users.
>
> ​+1. This will really help.
​


> Yeah, it might be useful. But it is fine to wait for seeing the above
> result.
> Maybe our motivation of the filter feature will become less after that ;)
>
> Thanks
> Ken Ohmichi
>
> ---
>
> >>
> >>
> >> Andreas
> >> --
> >>  Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
> >>   SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
> >>    GF: Felix Imendörffer, Jane Smithard, Graham Norton,
> >>        HRB 21284 (AG Nürnberg)
> >>     GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126
> >>
> >>
> >> ____________________________________________________________
> ______________
> >> OpenStack Development Mailing List (not for usage questions)
> >> Unsubscribe: OpenStack-dev-request at 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 at 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 at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20161203/4d829a2a/attachment.html>