Project

General

Profile

Actions
Copy link

action #44612

closed

Do we want to update http://tumblesle.qa.suse.de/ or decommision it?

Added by okurz over 5 years ago. Updated 3 months ago.

Status:
Resolved
Priority:
Low
Assignee:
okurz
Category:
-
Target version:
openQA Project - Ready
Start date:
2018-12-01
Due date:
% Done:

0%

Estimated time:

Description

http://tumblesle.qa.suse.de/

Actions
Copy link
 #1

Updated by szarate over 5 years ago

-1 from me (as in, yes, let's decomission it). Is it being actually used? las build or release seems to have been done back in 2017... :)

Actions
Copy link
 #2

Updated by okurz over 5 years ago

szarate wrote:

Is it being actually used?

I don't think this is how it works. No system was "used" at the time of invention, and most systems were not used from the beginning. I still consider the idea of tumblesle worthwhile.

Actions
Copy link
 #3

Updated by okurz over 5 years ago

  • Target version changed from Milestone 21 to Milestone 23
Actions
Copy link
 #4

Updated by okurz about 5 years ago

  • Target version changed from Milestone 23 to Milestone 25

I will try to do some convincing after my parental leave :)

Actions
Copy link
 #5

Updated by riafarov almost 5 years ago

  • Target version changed from Milestone 25 to future

@okurz, please, clarify the priorities. I do like the idea of the project, but I don't see much happening there that it becomes production ready and I have no time to invest in it right now.

Actions
Copy link
 #6

Updated by okurz almost 5 years ago

I am not sure what your definition of "production ready" is in this context. I had the opportunity to talk to some people and "TumbleSLE" is still something which quite some people like to see including PM, e.g. I talked to jwerner about it, rbrown, lkocman, behlert, etc. I would say the job of tumblesle.qa.suse.de could be to show that it is technically feasible for us to provide a usable system of SLE while it is still in development as well as help motivate dev+QA to keep the quality level high. The effort on the side of tooling to show the results is minimal, the effort on the side of Dev to keep a certain level of quality guaranteed during the development phase is a follow-up to that and probably more effort but probably also something that we in QA would really like. I can just offer the idea of TumbleSLE to motivate people and provide a longer-term vision. How much you within the QSF-u and QSF-y teams want to focus on short-term or long-term goals I will leave to you of course.

Actions
Copy link
 #7

Updated by mgriessmeier about 4 years ago

  • Status changed from New to Rejected

"Do we want to update http://tumblesle.qa.suse.de/ or decommision it?"

we want to decommision it.

Actions
Copy link
 #8

Updated by okurz about 4 years ago

but you didn't…

funny guy :D

Actions
Copy link
 #9

Updated by mgriessmeier about 4 years ago

  • Subject changed from [functional][y][u] Do we want to update http://tumblesle.qa.suse.de/ or decommision it? to Do we want to update http://tumblesle.qa.suse.de/ or decommision it?
  • Status changed from Rejected to In Progress
  • Assignee set to okurz

so the question was "Do we (as in u- or y-team) want to decomission it?"
the answer to that question is "yes".

We (as u- or y-team) don't feel responsible for that project, but we are also not the maintainers of this project, so we cannot give the final decision on that, nor decomission it ourselves.

I will remove team tags and assign to maintainer

could be nice idea for sle16 though ;)

Actions
Copy link
 #10

Updated by okurz about 4 years ago

  • Subject changed from Do we want to update http://tumblesle.qa.suse.de/ or decommision it? to [tools] Do we want to update http://tumblesle.qa.suse.de/ or decommision it?
  • Status changed from In Progress to Workable
  • Assignee deleted (okurz)
  • Priority changed from Normal to Low

yes, this makes sense. I consider this still a valid idea but I have to see how this fits into other concepts, e.g. ttm could be an alternative. As the webpage on http://tumblesle.qa.suse.de/ is still up and giving a good overview I would like to keep it running as is. Would be nice to add support for more recent SLE versions and also ensure the machine is maintained as other machines, e.g. using salt and such but not critical or top priority. Hence updating to include "[tools]", set to "Workable" but "Low" in "future".

Actions
Copy link
 #11

Updated by okurz over 3 years ago

  • Project changed from 46 to openQA Infrastructure
  • Subject changed from [tools] Do we want to update http://tumblesle.qa.suse.de/ or decommision it? to Do we want to update http://tumblesle.qa.suse.de/ or decommision it?
Actions
Copy link
 #12

Updated by okurz 3 months ago

  • Status changed from Workable to Resolved
  • Assignee set to okurz
  • Target version changed from future to Ready

http://tumblesle.qa.suse.de/ is still up and it's near-zero effort. The system is monitored and maintained in salt. Sometimes the system serves us as a very simple and stable platform for cross-checking.

Actions
Copy link

Also available in: Atom PDF