Original meeting minutes: https://etherpad.opensuse.org/p/ReleaseEngineering-20200611-s390x-openqa
Discussion about openSUSE/s390x
Attendees: Lubos, Oliver, Ihno Lubos: my understanding is that following is the issue https://progress.opensuse.org/issues/72880
Oliver: to summarize situation we don't have any commitment to get s390x maintaining Oliver this issue is currently specific for openSUSE: [o3][s390x] Early fail on s390x workers: connection refused https://progress.opensuse.org/issues/69328
Oliver: we need more commitment from QA department to maintain 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".
We are lucky to have Guillaume G. to keep ARM working. 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.
Oliver: We have a dedicated s390x "QE core" product owner for openQA tests, that is Timo Jyrinki https://confluence.suse.com/display/qasle/QE+squads+-+new+structure. The scope is basic test suite (install login and so on). For installer the product owner of the corresponding QE team is Rodion Iafarov.
Tasks:
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.
openqa.opensuse.org is available for administration for non-SUSE employees as well. See https://progress.opensuse.org/projects/openqav3/wiki/#Accessing-o3-infrastru... for details
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 they're online.
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 QE management.
Side note: we have only one power8 worker for openqa. Ihno: are build hosts and testing hosts in different network? Oliver: yes 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.
Lubos: I'll consinder the Power topic for Leap 15.3 interlock as well.
Hi,
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@suse.com An: "opensuse-factory@opensuse.org" opensuse-factory@opensuse.org Betreff: [opensuse-factory] Ad-hoc openSUSE s390x meeting 06.11.2020
Original meeting minutes: https://etherpad.opensuse.org/p/ReleaseEngineering-20200611-s390x-openqa
Discussion about openSUSE/s390x
Attendees: Lubos, Oliver, Ihno Lubos: my understanding is that following is the issue https://progress.opensuse.org/issues/72880
Oliver: to summarize situation we don't have any commitment to get s390x maintaining Oliver this issue is currently specific for openSUSE: [o3][s390x] Early fail on s390x workers: connection refused https://progress.opensuse.org/issues/69328
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 maintain 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 development? In my experience, there should be Admins for this job.
We are lucky to have Guillaume G. to keep ARM working. 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 Enterprise.
Oliver: We have a dedicated s390x "QE core" product owner for openQA tests, that is Timo Jyrinki https://confluence.suse.com/display/qasle/QE+squads+-+new+structure. The scope is basic test suite (install login and so on). For installer the product owner of the corresponding QE team is Rodion Iafarov.
Tasks:
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. https://lists.opensuse.org/opensuse-zsystems/2020-10/msg00000.html
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 issue case).
openqa.opensuse.org is available for administration for non-SUSE employees as well. See https://progress.opensuse.org/projects/openqav3/wiki/#Accessing-o3-infrastru... for details
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 they're online.
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 QE management.
Side note: we have only one power8 worker for openqa. Ihno: are build hosts and testing hosts in different network? Oliver: yes 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. N�����r��y隊Z)z{.���r�+�맲��r��z�^�ˬz��N�(�֜��^� ޭ隊Z)z{.���r�+��0�����Ǩ�
Best regards, Sarah
Hi Sarah,
On Friday, 6 November 2020 19.43.31 CET Sarah Julia Kriesch wrote:
Hi,
if you want to speak public about tickets, can you make these ones also public, please?
https://progress.opensuse.org/issues/69328 is public. https://progress.opensuse.org/issues/72880 was a wrong lead and does not add any useful information. But to satisfy curiousity: It was describing the problem that the s390x testing ressources assigned for the SUSE internal openQA instance dedicated for testing SUSE products was insufficient some time ago (years or month). This has actually been resolved a long time ago.
Gesendet: Freitag, 06. November 2020 um 16:18 Uhr Von: "Lubos Kocman" lubos.kocman@suse.com An: "opensuse-factory@opensuse.org" opensuse-factory@opensuse.org Betreff: [opensuse-factory] Ad-hoc openSUSE s390x meeting 06.11.2020
Original meeting minutes: https://etherpad.opensuse.org/p/ReleaseEngineering-20200611-s390x-openqa
Discussion about openSUSE/s390x
Attendees: Lubos, Oliver, Ihno Lubos: my understanding is that following is the issue https://progress.opensuse.org/issues/72880
Oliver: to summarize situation we don't have any commitment to get s390x maintaining Oliver this issue is currently specific for openSUSE: [o3][s390x] Early fail on s390x workers: connection refused https://progress.opensuse.org/issues/69328
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 maintain 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 development? In my experience, there should be Admins for this job.
Sorry about that. The phrasing is ambiguous. The SUSE team "QE Tools" ensures that the infrastructure of openqa.opensuse.org is well maintained. Though community members have access to the infrastructure (explained below). What I see as the responsibility of a "release manager" here is "fix tests, review the tests or getting the distribution published (not only for s390x)". And that does not even mean that such person would need to do the actual fixing, just ensuring that it happens by delegating to the right people to do that :) In my observation that is working out quite ok for openSUSE Tumbleweed and Leap for the architectures like x86_64, ppc64le, aarch64 and others.
We are lucky to have Guillaume G. to keep ARM working. 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 Enterprise.
Oliver: We have a dedicated s390x "QE core" product owner for openQA tests, that is Timo Jyrinki https://confluence.suse.com/display/qasle/QE+squads+-+new+structure. The scope is basic test suite (install login and so on). For installer the product owner of the corresponding QE team is Rodion Iafarov.
Tasks:
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. https://lists.opensuse.org/opensuse-zsystems/2020-10/msg00000.html
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 issue case).
I am very happy to hear that. I also want to offer my help and you are very welcome to contact me. For example I could explain some basics about the openQA setup and walk with you over basic steps of how the distribution(s) are currently tested in conjunction with openqa.opensuse.org, how test results are evaluated for publishing of new snapshots, etc.
openqa.opensuse.org is available for administration for non-SUSE employees as well. See https://progress.opensuse.org/projects/openqav3/wiki/#Accessing-o3-infrast ructure for details
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 they're online.
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 QE management.
Side note: we have only one power8 worker for openqa. Ihno: are build hosts and testing hosts in different network? Oliver: yes 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. :)
That would be lovely :) Also in case we see something missing in this context regarding openQA then we would be happy to look into according openQA feature requests ? or bug reports ;)
Lubos: I'll consinder the Power topic for Leap 15.3 interlock as well.
Best regards, Sarah
Have fun, Oliver
Hello Sarah,
Oliver must have already changed permissions. I could see both poo tickets without being logged in.
Sorry for any inconvenience.
On Fri, 2020-11-06 at 19:43 +0100, Sarah Julia Kriesch wrote:
Hi,
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@suse.com An: "opensuse-factory@opensuse.org" opensuse-factory@opensuse.org Betreff: [opensuse-factory] Ad-hoc openSUSE s390x meeting 06.11.2020
Original meeting minutes: https://etherpad.opensuse.org/p/ReleaseEngineering-20200611-s390x-openqa
Discussion about openSUSE/s390x
Attendees: Lubos, Oliver, Ihno Lubos: my understanding is that following is the issue https://progress.opensuse.org/issues/72880
Oliver: to summarize situation we don't have any commitment to get s390x maintaining Oliver this issue is currently specific for openSUSE: [o3][s390x] Early fail on s390x workers: connection refused https://progress.opensuse.org/issues/69328
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 maintain 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 development? In my experience, there should be Admins for this job.
We are lucky to have Guillaume G. to keep ARM working. 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 Enterprise.
Oliver: We have a dedicated s390x "QE core" product owner for openQA tests, that is Timo Jyrinki https://confluence.suse.com/display/qasle/QE+squads+-+new+structure . The scope is basic test suite (install login and so on). For installer the product owner of the corresponding QE team is Rodion Iafarov.
Tasks:
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. https://lists.opensuse.org/opensuse-zsystems/2020-10/msg00000.html
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 issue case).
openqa.opensuse.org is available for administration for non-SUSE employees as well. See https://progress.opensuse.org/projects/openqav3/wiki/#Accessing-o3-infrastru... for details
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 they're online.
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 QE management.
Side note: we have only one power8 worker for openqa. Ihno: are build hosts and testing hosts in different network? Oliver: yes 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. N�����r��y隊Z)z{.���r�+�맲��r��z�^�ˬz��N�(�֜��^� ޭ隊Z)z{.���r�+�� 0�����Ǩ�
Best regards, Sarah
Hi Sarah!
On 11/6/20 7:43 PM, Sarah Julia Kriesch wrote:
You don't have to look long. You have got an openSUSE Member and IBM employee in the community. https://lists.opensuse.org/opensuse-zsystems/2020-10/msg00000.html
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 issue case).
In case there is any interest from IBM's side regarding Debian on s390x, Debian currently has no dedicated maintainer for the s390x port in the upcoming Bullseye release [1].
So, in case there is any interest from IBM's side with regard Debian's s390x port, I suggest reaching out to the debian-s390 mailing list.
(Yes, I know this is the openSUSE Factory list ;-)).
Adrian
[1] https://lists.debian.org/debian-s390/2020/11/msg00001.html
Hi Adrian,
Gesendet: Montag, 23. November 2020 um 12:41 Uhr Von: "John Paul Adrian Glaubitz" adrian.glaubitz@suse.com An: "Sarah Julia Kriesch" ada.lovelace@gmx.de Cc: "opensuse-factory@opensuse.org" opensuse-factory@opensuse.org Betreff: [opensuse-factory] Re: Ad-hoc openSUSE s390x meeting 06.11.2020
Hi Sarah!
On 11/6/20 7:43 PM, Sarah Julia Kriesch wrote:
You don't have to look long. You have got an openSUSE Member and IBM employee in the community. https://lists.opensuse.org/opensuse-zsystems/2020-10/msg00000.html
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 issue case).
In case there is any interest from IBM's side regarding Debian on s390x, Debian currently has no dedicated maintainer for the s390x port in the upcoming Bullseye release [1].
Debian is on our list with supported community Linux distributions [0].
So, in case there is any interest from IBM's side with regard Debian's s390x port, I suggest reaching out to the debian-s390 mailing list.
We are open for additional Linux Contributors joining IBM (Debian is not excluded). The rule in our "Linux on Z" department is, that applicants with community memberships (in open-source projects) should receive an approval (firstly for the free time). I have received this commitment last year before my application.
In my case, I am openSUSE Member and no Debian Developer. I know that some of you wanted to support me to become one. But the time was missing besides my studies and my volunteering as a Student Senator.
The next step is to integrate your hobby into the job then. IBM is open for great ideas by their employees. I wrote into my proposal that it can be that some contributions could become part of Debian. ;-) I am pro improving the collaboration with all important Linux distributions. We are living equality (of Linux distributions - especially our Linux partners) here. :-) It is naturally that Enterprise distribution partners have got a higher priority. If you want to join as a Debian Developer or an openSUSE Member, then you can introduce the open-source culture of your community in your team. We want to expand that. :-)
(Yes, I know this is the openSUSE Factory list ;-)).
Adrian
Best regards, Sarah
[0] https://developer.ibm.com/blogs/the-latest-on-open-source-software-for-ibm-z...
[1] https://lists.debian.org/debian-s390/2020/11/msg00001.html
openSUSE Factory mailing list -- factory@lists.opensuse.org To unsubscribe, email factory-leave@lists.opensuse.org List Netiquette: https://en.opensuse.org/openSUSE:Mailing_list_netiquette List Archives: https://lists.opensuse.org/archives/list/factory@lists.opensuse.org
Hi!
On 11/6/20 4:18 PM, Lubos Kocman wrote:
Oliver: to summarize situation we don't have any commitment to get s390x maintaining Oliver this issue is currently specific for openSUSE: [o3][s390x] Early fail on s390x workers: connection refused https://progress.opensuse.org/issues/69328
The main problem with s390x is that the hardware is way more expensive to what normal people within an open source community can afford.
It would actually be nice if IBM developed a slimmed down version of the s390x hardware purely for community purposes, i.e. some sort of evaluation board.
I would also be still interested in getting more architectures added to openSUSE but so far there seems to be zero interest from the community.
In Debian, I'm maintaining ports for multiple architectures including Alpha, HPPA, Motorola 68000, 32-bit and 64-bit PowerPC (BE), SuperH and SPARC. It would be nice to have openSUSE built on some of these as well (except for PPC which we already have). Especially SPARC would be cool as the hardware is extremely fast (up to 5 GHz, 32 cores).
Adrian
On Mon, 9 Nov 2020 13:58:38 +0100, John Paul Adrian Glaubitz adrian.glaubitz@suse.com wrote:
Hi!
On 11/6/20 4:18 PM, Lubos Kocman wrote:
Oliver: to summarize situation we don't have any commitment to get s390x maintaining Oliver this issue is currently specific for openSUSE: [o3][s390x] Early fail on s390x workers: connection refused https://progress.opensuse.org/issues/69328
The main problem with s390x is that the hardware is way more expensive to what normal people within an open source community can afford.
It would actually be nice if IBM developed a slimmed down version of the s390x hardware purely for community purposes, i.e. some sort of evaluation board.
That would be awesome, but I don't have high hopes
Others would be helpful too: e.g. HP's Itanium and PA-RISC2
I would also be still interested in getting more architectures added to openSUSE but so far there seems to be zero interest from the community.
In Debian, I'm maintaining ports for multiple architectures including Alpha, HPPA, Motorola 68000, 32-bit and 64-bit PowerPC (BE), SuperH and SPARC. It would be nice to have openSUSE built on some of these as well (except for PPC which we already have). Especially SPARC would be cool as the hardware is extremely fast (up to 5 GHz, 32 cores).
Adrian
Gesendet: Montag, 09. November 2020 um 14:27 Uhr Von: "H.Merijn Brand" linux@tux.freedom.nl An: "John Paul Adrian Glaubitz" adrian.glaubitz@suse.com Cc: opensuse-factory@opensuse.org Betreff: Re: [opensuse-factory] Ad-hoc openSUSE s390x meeting 06.11.2020
On Mon, 9 Nov 2020 13:58:38 +0100, John Paul Adrian Glaubitz adrian.glaubitz@suse.com wrote:
Hi!
On 11/6/20 4:18 PM, Lubos Kocman wrote:
Oliver: to summarize situation we don't have any commitment to get s390x maintaining Oliver this issue is currently specific for openSUSE: [o3][s390x] Early fail on s390x workers: connection refused https://progress.opensuse.org/issues/69328
The main problem with s390x is that the hardware is way more expensive to what normal people within an open source community can afford.
It would actually be nice if IBM developed a slimmed down version of the s390x hardware purely for community purposes, i.e. some sort of evaluation board.
That would be awesome, but I don't have high hopes
IBM is sponsoring something as that via the Open Mainframe Project. https://www.openmainframeproject.org/
Everybody can receive free access to a LinuxONE instance to test his software. We want to provide communities all what is necessary to develop for s390x.
Others would be helpful too: e.g. HP's Itanium and PA-RISC2
I would also be still interested in getting more architectures added to openSUSE but so far there seems to be zero interest from the community.
In Debian, I'm maintaining ports for multiple architectures including Alpha, HPPA, Motorola 68000, 32-bit and 64-bit PowerPC (BE), SuperH and SPARC. It would be nice to have openSUSE built on some of these as well (except for PPC which we already have). Especially SPARC would be cool as the hardware is extremely fast (up to 5 GHz, 32 cores).
Adrian
Best regards, Sarah
-- H.Merijn Brand https://tux.nl Perl Monger http://amsterdam.pm.org/ using perl5.00307 .. 5.33 porting perl5 on HP-UX, AIX, and Linux https://useplaintext.email https://www.test-smoke.org http://qa.perl.org http://www.goldmark.org/jeff/stupid-disclaimers/
Hello!
On 11/9/20 2:41 PM, Sarah Julia Kriesch wrote:
That would be awesome, but I don't have high hopes
IBM is sponsoring something as that via the Open Mainframe Project. https://www.openmainframeproject.org/
Everybody can receive free access to a LinuxONE instance to test his software. We want to provide communities all what is necessary to develop for s390x.
Yeah, I'm aware of these offerings but having a dedicated machine with full root access would still be nicer to tinkle around.
For Debian Ports, IBM generously donated one POWER to which I have full access and I can even test kernel patches with. Not sure how far I would get there with the Open Mainframe Project.
Adrian
On Mon, 2020-11-09 at 15:07 +0100, John Paul Adrian Glaubitz wrote:
Hello!
On 11/9/20 2:41 PM, Sarah Julia Kriesch wrote:
That would be awesome, but I don't have high hopes
IBM is sponsoring something as that via the Open Mainframe Project. https://www.openmainframeproject.org/
Everybody can receive free access to a LinuxONE instance to test his software. We want to provide communities all what is necessary to develop for s390x.
Yeah, I'm aware of these offerings but having a dedicated machine with full root access would still be nicer to tinkle around.
For Debian Ports, IBM generously donated one POWER to which I have full access and I can even test kernel patches with. Not sure how far I would get there
I was told that the amount of VMs that we can request from SUSE has no hard limit. If you have some usecases please share then with us and we can see what can be done about it.
with the Open Mainframe Project.
Adrian
On Monday, 9 November 2020 14.41.34 CET Sarah Julia Kriesch wrote:
Gesendet: Montag, 09. November 2020 um 14:27 Uhr Von: "H.Merijn Brand" linux@tux.freedom.nl An: "John Paul Adrian Glaubitz" adrian.glaubitz@suse.com Cc: opensuse-factory@opensuse.org Betreff: Re: [opensuse-factory] Ad-hoc openSUSE s390x meeting 06.11.2020
On Mon, 9 Nov 2020 13:58:38 +0100, John Paul Adrian Glaubitz
adrian.glaubitz@suse.com wrote:
Hi!
On 11/6/20 4:18 PM, Lubos Kocman wrote:
Oliver: to summarize situation we don't have any commitment to get s390x maintaining Oliver this issue is currently specific for openSUSE: [o3][s390x] Early fail on s390x workers: connection refused https://progress.opensuse.org/issues/69328
The main problem with s390x is that the hardware is way more expensive to what normal people within an open source community can afford.
It would actually be nice if IBM developed a slimmed down version of the s390x hardware purely for community purposes, i.e. some sort of evaluation board.
That would be awesome, but I don't have high hopes
IBM is sponsoring something as that via the Open Mainframe Project. https://www.openmainframeproject.org/
Do you think it would be possible to use this as "openQA workers"?
On Mon, 2020-11-09 at 17:27 +0100, Oliver Kurz wrote:
On Monday, 9 November 2020 14.41.34 CET Sarah Julia Kriesch wrote:
IBM is sponsoring something as that via the Open Mainframe Project. https://www.openmainframeproject.org/
Do you think it would be possible to use this as "openQA workers"?
It wasn't when I looked at it when the Open Mainframe project started in 2015
Regards,
Gesendet: Montag, 09. November 2020 um 17:35 Uhr Von: "Richard Brown" rbrown@suse.de An: opensuse-factory@opensuse.org Betreff: Re: [opensuse-factory] Ad-hoc openSUSE s390x meeting 06.11.2020
On Mon, 2020-11-09 at 17:27 +0100, Oliver Kurz wrote:
On Monday, 9 November 2020 14.41.34 CET Sarah Julia Kriesch wrote:
IBM is sponsoring something as that via the Open Mainframe Project. https://www.openmainframeproject.org/
Do you think it would be possible to use this as "openQA workers"?
Travis CI is using the LinuxONE Community Cloud (for s390x tests for open source projects on Github available), too.
I can ask, whether we are allowed to do that with openQA. I believe, that we will be asked why we don't use the SUSE mainframe.
It wasn't when I looked at it when the Open Mainframe project started in 2015
Best regards, Sarah
Regards,
-- Richard Brown Linux Distribution Engineer - Future Technology Team
Phone +4991174053-361 SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, D-90409 Nuernberg (HRB 36809, AG Nürnberg) Geschäftsführer: Felix Imendörffer
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 11/9/20 2:27 PM, H.Merijn Brand wrote:
It would actually be nice if IBM developed a slimmed down version of the s390x hardware purely for community purposes, i.e. some sort of evaluation board.
That would be awesome, but I don't have high hopes
Others would be helpful too: e.g. HP's Itanium and PA-RISC2
PA-RISC is very stable and has rather good upstream support (toolchain and kernel). The only thing that's currently missing is LLVM/Rust and OpenJDK Zero due to the fact that HPPA has an upward-growing stack (why would anyone do that ;-)). I have started working on OpenJDK Zero for PA-RISC though and will finish it at some point.
Itanium is currently a bit more tricky. For one, kernels > 4.14 don't run on larger NUMA systems and the other thing is that Ruby 2.7 dropped support for Itanium. OpenJDK runs fine, LLVM/Rust is missing as LLVM dropped IA64 support at some point.
M68k is very promising as it has a very strong community, especially for being such an old port and is even about to get an LLVM backend [1] (which means Rust on the Amiga :D). We also recently got a new QEMU pure virtual machine type for M68k [2] which will make the target very attractive for OBS. I would love to see a public m68k openSUSE port in OBS, that would be really cool.
Adrian
[1] https://www.youtube.com/watch?v=-6zXXPRl-QI [2] https://www.youtube.com/watch?v=s_ve0bCC9q4
On Monday 2020-11-09 21:20, John Paul Adrian Glaubitz wrote:
PA-RISC [...] has an upward-growing stack (why would anyone do that ;-)).
Why would anyone define electrons as "negative" and protons as "positive" and not vice versa...
Maybe there is a hardware cost to the stack direction. On the matter of RISC-V being little-endian over big-endian, I seem to recall that Sifive at Fosdem said it was about a bit of circuitry, BE needing somewhat more than an LE machine.
John Paul Adrian Glaubitz wrote:
Hi!
On 11/6/20 4:18 PM, Lubos Kocman wrote:
Oliver: to summarize situation we don't have any commitment to get s390x maintaining Oliver this issue is currently specific for openSUSE: [o3][s390x] Early fail on s390x workers: connection refused https://progress.opensuse.org/issues/69328
The main problem with s390x is that the hardware is way more expensive to what normal people within an open source community can afford.
About twenty years ago I ran SUSE Linux/390 and SAPDB on the Hercules emulator, worked quite well. Slow, but functional.
-
H.Merijn Brand -
Jan Engelhardt -
John Paul Adrian Glaubitz -
Lubos Kocman -
Oliver Kurz -
Per Jessen -
Richard Brown -
Sarah Julia Kriesch