Project

General

Profile

Actions

coordination #124721

closed

coordination #121720: [saga][epic] Migration to QE setup in PRG2+NUE3 while ensuring availability

coordination #116623: [epic] Migration of SUSE Nbg based openQA+QA+QAM systems to new security zones

[epic] Ensure proper QE maintainership of Nbg QAM machines

Added by okurz about 1 year ago. Updated 7 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Target version:
Start date:
2023-02-17
Due date:
% Done:

100%

Estimated time:
(Total: 0.00 h)

Description

Motivation

With the work on #116623 it became clear that we want to have any QAM machines now treated as a joint "QE" group, including not only IP range, domain, etc., but also physical machines, their maintainership and administration. With this we should ensure that all former Nbg QAM machines are maintained by the SUSE QE Tools team. The SUSE QE Tools team will take responsibility, ensure maintainership, make decisions. This was also clarified with the line managers of the former contact persons who like to focus on other areas of work.

Acceptance criteria

Suggestions

  • We clarified that it's a better option to update the racktables entries to "qa-team@suse.de" with a comment pointing to the former "contact person" who can still be asked for information or specific help.
  • With the whole team walk over all machines in racktables to get accustomed.
  • Where we see the need plan according work, e.g. to move some machines and such.

Subtasks 3 (0 open3 closed)

action #124724: Ensure Nbg QAM machines have a current maintainer as "contact person" size:SResolvedokurz2023-02-17

Actions
action #125144: Give members of SUSE QE Tools team a chance to get familiar with Nbg QAM machines size:MResolvedokurz2023-02-17

Actions
action #125234: Decommission obsolete machines in qam.suse.de size:MResolvedokurz2023-03-01

Actions
Actions #1

Updated by okurz 12 months ago

  • Target version changed from future to Ready
Actions #2

Updated by livdywan 12 months ago

  • Status changed from New to Blocked
  • Assignee set to livdywan
Actions #3

Updated by okurz 12 months ago

  • Project changed from 175 to 46
  • Category set to Infrastructure
Actions #4

Updated by okurz 9 months ago

  • Status changed from Blocked to Resolved
  • Assignee changed from livdywan to okurz

All subtasks resolved, all ACs covered.

Actions

Also available in: Atom PDF