if you want to speak public about tickets, can you make these ones also public, please?
Gesendet: Freitag, 06. November 2020 um 16:18 Uhr
Von: "Lubos Kocman" <lubos.kocman(a)suse.com>
An: "opensuse-factory(a)opensuse.org" <opensuse-factory(a)opensuse.org>
Betreff: [opensuse-factory] Ad-hoc openSUSE s390x meeting 06.11.2020
Original meeting minutes:
Discussion about openSUSE/s390x
Attendees: Lubos, Oliver, Ihno
Lubos: my understanding is that following is the issue
Oliver: to summarize situation we don't have any commitment to get
Oliver this issue is currently specific for openSUSE: [o3][s390x] Early
fail on s390x workers: connection refused
The community is waiting for that since months.
We can not do anything in this direction, because the mainframe is in the SUSE network.
Oliver: we need more commitment from QA department to
openQA/s390x or even SUSE as a whole.
Ihno: number of s390x guests has no real limits.
Oliver: when we talk about openSUSE, the very single instance was
either not fully used or working.
Ihno: I can work on the cases where guests are not working.
Oliver: I'm Product Owner for maintaining openQA as a software as well
as the infrastructure of openqa.opensuse.org
. What is outside our scope
is to fix tests, review the tests or getting the distribution published
(not only for s390x). That is responsibility of "release managers".
Really? Is a Release Manager responsible for a working infrastructure for
In my experience, there should be Admins for this job.
We are lucky to have Guillaume G. to keep ARM
okurz was asked by Andrew Waafa at an openSUSE Conference what could be
done and the advice was to simply ask every day or as often as possible
about the state of the builds, why tests are not executed, report
tickets, find the right people to delegate to, etc. . Agreement with
Andrew Waffa in discussion to make openSUSE/ARM a thing
Ihno: it will be our top priority to get s390x/openQA working. If you
need HW resources, we can give it to you.
Lubos: we need to revisit our current dedicated QA resources with
introduction of s390x in Leap
Oliver: I don't think that the current contract works, reality is more
like a reactive support which is nice but either there is no one asking
or tickets are not properly triaged and ignored.
Ihno: externals can only do just a certain part of openQA work, many
things have to be done by SUSE employees.
I agree. And that is the case here, too.
SUSE is owner of the mainframe, because it has been used mainly for SUSE Linux
Oliver: We have a dedicated s390x "QE core"
product owner for openQA
tests, that is Timo Jyrinki
The scope is basic test suite (install login and so on). For installer
the product owner of the corresponding QE team is Rodion Iafarov.
Lubos to talk to Marita or possibly Ralf regarding dedicated resources
in Leap 15.3 interlock document. We have more arches to support, we'll
need more people to maintain openqa as well. Note by okurz: The
important point to reach is the common understanding that openSUSE is
part of SUSE's business. IBM are interested and happy about any "good
publicity" for IBM Mainframes, i.e. s390x.
Lubos to see if we can find external IBM s390x/openSUSE contact. The
problem is that the person would not have the possibility to fix all of
the openqa issues due to the fact that some issues can be addressed
only by SUSE Employees.
You don't have to look long.
You have got an openSUSE Member and IBM employee in the community.
I have been working for IBM since October and have received the approval for openSUSE
contributions at the end of the month.
This week we had a small discussion how to proceed.
IBM is watching that as a win-win situation to receive an openSUSE Member as an employee.
We want to improve the cooperation on this way.
I can do all necessary from IBM side. But I can not do that inside of SUSE (the mainframe
is available for administration
employees as well. See
Ihno: to reach out to Ralf U. regarding importance of s390x/openSUSE
openqa and basic ticket triaging as a responsibility for the QE
department. Current situation is bad no tests were finished in last 6
months or so and nothing was even communicated in tickets.
Ihno: revisit current s390x resources for openQA. And make sure that
Oliver: I will update ticket and link it accordingly, but I would be
really happy if Release Manager can first get commitment from not-only
Side note: we have only one power8 worker for openqa.
Ihno: are build hosts and testing hosts in different network?
Success story from ARM: external machines not maintained by QE Tools
team (within SUSE). openQA and openqa.opensuse.org
can and is using any
machine that is reachable over internet with sufficient bandwidth, e.g.
cloud instances, physical machines at SUSE partners, etc. This is an
opportunity for SUSE partners to have easier access with less effort to
contribute to the testing of openSUSE and SUSE distributions.
I hope, that we can have that with IBM in the future, too. :)
Lubos: I'll consinder the Power topic for Leap 15.3 interlock as well.
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org