[qe-core][functional][saga] remote system management: salt, sles+suma, sles+storage (terraform, kubernetes, etc.)
#1 Updated by maritawerner about 4 years ago
Yes, agreed, we need to get more information here from different parties. I know also that James from QA CSS got some requests here. And there is a workshop plannend for "Interoperability" from November 20-22 where this topic is also covered.
#4 Updated by maritawerner over 3 years ago
In the workshop we agreed that this is an important topic to follow. In addition I had a short discussion with Stefan Behlert and he told me that we have to wait what will come with the next SP of SLe 15 and then the products on top have to adjust and then we can have a combined testing.
#5 Updated by maritawerner over 3 years ago
In a follow-up meting of the interoperability workshop the new SUSE readmap was presented:
It seems that there are major changes ongoing in the was SUSE Products are set-up. So testing products together is really a higher management level discussion that has to be addressed in PRDs and Interlocks. I think we could close that ticket here for now.
#8 Updated by okurz over 2 years ago
- Status changed from Rejected to New
No, you seem to miss the point. This is a "break down the silos" task. The part about "I don't know what the other team is doing and I don't care" is the problem that needs to be solved here. Our customers are told "SUSE offers this awesome stack of component that nicely fit together" but if we don't ever run them together that story is very unlikely to be true.
#10 Updated by szarate about 2 years ago
See for the reason of tracker change: http://mailman.suse.de/mailman/private/qa-sle/2020-October/002722.html
#11 Updated by tjyrinki_suse about 2 years ago
- Subject changed from [functional][u][saga] remote system management: salt, sles+suma, sles+storage (terraform, kubernetes, etc.) to [qe-core][functional][saga] remote system management: salt, sles+suma, sles+storage (terraform, kubernetes, etc.)
- Parent task deleted (
#12 Updated by okurz about 1 year ago
I came to this ticket due to periodically reviewing tickets as described on https://progress.opensuse.org/projects/openqatests/wiki#How-we-work-on-tickets
This ticket was set to "Normal" priority but was not updated within the SLO period for "Normal" tickets (365 days) as described on https://progress.opensuse.org/projects/openqatests/wiki/Wiki#SLOs-service-level-objectives
First reminder: Please consider picking up this ticket within the next 365 days or just set the ticket to the next lower priority of "Low" (no SLO related time period).