action #52004
closedEnable SUSE partners to test SLE using openQA in the open easily
0%
Description
Motivation¶
As a SUSE partner I can execute openQA SLE tests based on the existing tests, e.g. in os-autoinst-distri-opensuse so that I do not need to rely on SUSE internal testing of SLE only or re-invent automated tests. This came up in a discussion with our partner IBM.
Open points¶
- os-autoinst-distri-opensuse is open and free already but os-autoinst-needles-opensuse includes (only) the openSUSE needles, os-autoinst-needles-sle is internal
- DONE:
Is anyone outside allowed to run e.g. Beta versions of SLE?-- okurz: I don't know what I meant with that question. Obviously Beta versions are meant to be used by non-SUSE employees - Would someone outside SUSE be allowed to publish SLE needles on his own?
- Is there a difference for Alpha/Beta/RC period?
- Would we be able to provide the internal needles to SUSE partners (when they promise to not disclose them)?
- DONE:
Updated by okurz about 4 years ago
- Description updated (diff)
- Assignee set to maritawerner
- Target version changed from Ready to future
I am not sure why I originally reported the ticket in the "openQA Project" as it seems more fitting to "openQA Tests". I will keep the ticket in the main project, maybe there are things we can improve on the upstream openQA side still.
@maritawerner can you help to find answers to the questions in the ticket? If we find a better and supportive message we can motivate for more use of our automated openQA tests by Beta testers to be able to scale our testing better and not rely on only SUSE-internal QA.
Updated by maritawerner over 3 years ago
Q: Is there a difference for Alpha/Beta/RC period?
A: Yes. The official Interlock for the product happens in the Alpha phase. The beta phase can only start when the product is interlocked, aka acknowledged by all E&I departments, Product Management and also by the upper management. Then the Beta program for interested SUSE partners can start and they can download the beta milestones and snapshots. The Beta dn RC phase are the same in this regard.
Updated by maritawerner over 3 years ago
About question 1 and 3: I think it could be possible to provide the needles to Beta program participants but I have never heard of any interest here. I can ask Vincent Moutoussamy if he is aware of any partner interest (email sent)
In addition to that I have presented openQA to several partners/customers, e.g. IBM, GE Healthcare, Dailmer, B1 Systems, (HPE?) and I have never seen any use of openQA. Maybe some of them joined the openQA community but I could not see any follow-up in some official meetings. So I doubt that the partners really use openQA and would need any SLE needles.
Updated by okurz over 3 years ago
maritawerner wrote:
About question 1 and 3: I think it could be possible to provide the needles to Beta program participants but I have never heard of any interest here. I can ask Vincent Moutoussamy if he is aware of any partner interest (email sent)
The motivation of the ticket already states it: "This came up in a discussion with our partner IBM." so that means that there is partner interest.
In addition to that I have presented openQA to several partners/customers, e.g. IBM, GE Healthcare, Dailmer, B1 Systems, (HPE?) and I have never seen any use of openQA. Maybe some of them joined the openQA community but I could not see any follow-up in some official meetings. So I doubt that the partners really use openQA and would need any SLE needles.
Partners do use openQA already, e.g. within the openSUSE community. But for SLE testing partners would have a hard time using openQA without SLE needles but even that was tried at least once (don't remember the details). So this is why I suggest to provide needles as much as possible. Also keep in mind that we want to be "QE" and not do "QA" solely on our own but enable others to do it where it makes sense.
Updated by maritawerner about 3 years ago
Again, I have heard that many times that partners are interested in openQA. Either they are engaged already in the openSUSE community or they have dropped the topic. I think we can close that ticket. If some part er speaks up again we can talk to him directly, I do not need this ticket for that.
Updated by okurz about 3 years ago
- Status changed from New to Resolved
- Assignee changed from maritawerner to okurz
Fine for me. So I understand that the general message from SUSE here is to partners that collaboration should happen on the base of openSUSE which can be even more attractive after the sucessful conclusion of the "Jump" project. Let's call it "Resolved" as such with this message.