Project

General

Profile

Actions
Copy link

action #125144

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

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 almost 2 years ago. Updated almost 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
okurz
Target version:
openQA Project (public) - Ready
Start date:
2023-02-17
Due date:
% Done:

0%

Estimated time:
Tags:
qam, infra, racktables

Description

Motivation

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

Suggestions

  • 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
Copy link
 #1

Updated by okurz almost 2 years ago

  • Project changed from 175 to QA (public)
  • Parent task changed from #116623 to #124721
Actions
Copy link
 #2

Updated by okurz almost 2 years ago

  • Tracker changed from coordination to action
Actions
Copy link
 #3

Updated by okurz almost 2 years ago

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

Updated by okurz almost 2 years ago

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

I pinged the team in https://suse.slack.com/archives/C02AJ1E568M/p1677589678801479

@here MOB session this Thursday about https://progress.opensuse.org/issues/125144 . Easy walkthrough over racktables entries

Actions
Copy link
 #5

Updated by okurz almost 2 years ago

  • Status changed from Feedback to In Progress

An important question came up in https://suse.slack.com/archives/C02CANHLANP/p1677660140363379?thread_ts=1677659850.557169&cid=C02CANHLANP 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 https://gitlab.suse.de/qa-maintenance/infrastructure/-/issues but I worry we would strain the original team scope and member's motivation. Can we say that https://gitlab.suse.de/qa-maintenance/infrastructure/-/issues is owned and maintained by the UV squad and for any low-level hardware related requests you can create according tickets within progress.opensuse.org/projects/qa/ or a corresponding sub-project which the SUSE QE Tools team would track.

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

Actions
Copy link
 #6

Updated by okurz almost 2 years ago

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

We conducted a walkthrough and feel good about it

Actions
Copy link

Also available in: Atom PDF