action #125144


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

coordination #124721: [epic] Ensure proper QE maintainership of Nbg QAM machines

Give members of SUSE QE Tools team a chance to get familiar with Nbg QAM machines size:M

Added by livdywan over 1 year ago. Updated over 1 year ago.

Target version:
Start date:
Due date:
% Done:


Estimated time:



We agreed to take over consistent maintainership of those machines and should be sure we know what we're signing up for.

Acceptance criteria

  • AC1: The SUSE QE Tools team knows the basics about the Nbg QAM machines and feels in a position to make relevant decisions


  • With the whole team walk over all machines in racktables to get accustomed.
  • Conduct a mob session with multiple team members (in the regular slot or ad-hoc, whichever is convenient)
Actions #1

Updated by okurz over 1 year ago

  • Project changed from 175 to QA
  • Parent task changed from #116623 to #124721
Actions #2

Updated by okurz over 1 year ago

  • Tracker changed from coordination to action
Actions #3

Updated by okurz over 1 year ago

  • Tags set to infra, qam, racktables
Actions #4

Updated by okurz over 1 year ago

  • Due date set to 2023-03-14
  • Status changed from Workable to Feedback
  • Assignee set to okurz

I pinged the team in

@here MOB session this Thursday about . Easy walkthrough over racktables entries

Actions #5

Updated by okurz over 1 year ago

  • Status changed from Feedback to In Progress

An important question came up in by hrommel:

that implies that for handling issues with reference hosts we will switch from using the infra project in gitlab to POO ?

My suggestion:

It would be technically possible for the tools team to watch but I worry we would strain the original team scope and member's motivation. Can we say that is owned and maintained by the UV squad and for any low-level hardware related requests you can create according tickets within or a corresponding sub-project which the SUSE QE Tools team would track.

But I am interested in team's feedback on this.

Actions #6

Updated by okurz over 1 year ago

  • Due date deleted (2023-03-14)
  • Status changed from In Progress to Resolved

We conducted a walkthrough and feel good about it


Also available in: Atom PDF