Sorry for the late reply, I was on vacation and wasn't able to participate in the meeting.

I'm interested to maintain the subunit2sql and help with maintenance of openstack-health.

Kind regards,

Arx Cruz

On Mon, Jan 3, 2022 at 11:25 AM Martin Kopec <mkopec@redhat.com> wrote:

A little late but here is what we have concluded in the call:

* TripleO's dashboard is not as similar to the openstack-health's one as we initially thought, it lacks the most important functionality for us which shows a pass/fail rate of a particular test

* TripleO team would be interested in having test pass/fail rate functionality

* In order to make openstack-health working again:

** openstack/openstack-health's codebase needs to be updated

** operational assistance to deploy the service as well as the subunit2sql processing pipeline and the subunit2sql database backend is required (see Clark's email within this thread)

** we need a point of contact for regular maintenance of the service, infra issues and etc

* If a volunteer who would work on the mentioned action items is found, infra team can provide needed resources and guidance - remember that the main reason the tool is being shutdown is only the lack of a maintainer

* In the meantime QA team will start retirement process of the openstack-health repository

If you would like to get included in this and provide any help, feel free to reach out to us.

Thanks,

On Thu, 9 Dec 2021 at 17:23, Martin Kopec <mkopec@redhat.com> wrote:

We're gonna have a call to discuss collaboration between qa and tripleo and the next steps regarding openstack-health.

The call details:

next Thursday December 16th 1630 UTC

Video call link: https://meet.google.com/cmr-yzaq-twp

Feel free to join,

On Wed, 1 Dec 2021 at 17:52, Ronelle Landy <rlandy@redhat.com> wrote:

On Wed, Dec 1, 2021 at 11:11 AM Ghanshyam Mann <gmann@ghanshyammann.com> wrote:

Hello Everyone,

In the QA meeting[1], we discussed the help needed to maintain the OpenStack health dashboard which is
broken currently and the QA team does not have the JS developer and bandwidth to fix it. While discussing
it meeting, we found that the TripleO team might be working on a similar dashboard for their CI results. If that
is the case, can we collaborate on maintaining the existing dashboard?

We had a discussion with Martin Kopec about collaboration with QA in maintaining a TripleO focused dashboard.

We have two dashboards in progress at the moment  - one focused on jobs running in https://review.rdoproject.org/zuul/status  - 

 http://ci-health-rdo.tripleo.org/ and one where we are starting to track failures in select jobs running on https://zuul.openstack.org/ - http://ci-health.tripleo.org/

If you would like to collaborate on this work, please ping us on #oooq on (OFTC) join our community call on Tuesdays at 1:30pm UTC and we can discuss further.

Thanks!

OpenStack health dashboard: https://opendev.org/openstack/openstack-health
Repo: http://status.openstack.org/openstack-health/#/

[1] https://meetings.opendev.org/meetings/qa/2021/qa.2021-11-16-15.00.log.html#l-71

-gmann

--

Martin Kopec
Senior Software Quality Engineer
Red Hat EMEA

--

Martin Kopec
Senior Software Quality Engineer
Red Hat EMEA

--

Arx Cruz

Software Engineer

Red Hat EMEA

arxcruz@redhat.com   

@RedHat   Red Hat   Red Hat