Project

General

Profile

Actions

action #181151

open

coordination #161414: [epic] Improved salt based infrastructure management

Follow-up steps regarding backup.qa.suse.de (and backup.qe.prg2.suse.org)

Added by livdywan 12 days ago. Updated 7 days ago.

Status:
New
Priority:
Low
Assignee:
Category:
Feature requests
Start date:
Due date:
% Done:

0%

Estimated time:
Tags:

Description

Motivation

We previously found that the storage was unreliable. As of #173674 we have a new backup setup on openplatform. We should discuss what to do with the old backup.qa.suse.de and if it's to be removed, or used as a fallback. If we decide to delete the VM we may want to ensure that we have an additional backup option.

Acceptance criteria

  • AC1: The current and former role of backup.qa.suse.de is clearly described on wiki pages
  • AC2: backup.qa.suse.de is no longer required by any salt states OR clearly identified as a fallback
  • AC3: Additional backup options have been considered

Suggestions


Related issues 1 (0 open1 closed)

Copied from openQA Infrastructure (public) - action #173674: qamaster-independent backup size:SResolveddheidler2024-12-03

Actions
Actions #1

Updated by livdywan 12 days ago

  • Copied from action #173674: qamaster-independent backup size:S added
Actions #2

Updated by livdywan 12 days ago

  • Target version changed from Ready to Tools - Next

I suppose it shouldn't wait too long, since we also want to be sure documentation is updated and we don't end up confused what was or wasn't already done. But shouldn't need to be on the backlog right away.

Actions #3

Updated by okurz 9 days ago

  • Assignee set to okurz

I don't agree with the ACs. Why should we get rid of backup.qa.suse.de? As long as we can still run it that is good as an additional safety layer. What should be done however is to ensure that our current backup solution is mentioned on https://gitlab.suse.de/suse/wiki/-/blob/main/qe_infrastructure.md

Actions #4

Updated by livdywan 7 days ago

As of 2025-04-20 backup.qa.suse.de was replaced by backup.qe.prg2.suse.org.

Related change: https://gitlab.suse.de/suse/wiki/-/commit/0e4317a19d736a50b136f80a8fb7d8c9b569a014

okurz wrote in #note-3:

I don't agree with the ACs. Why should we get rid of backup.qa.suse.de? As long as we can still run it that is good as an additional safety layer. What should be done however is to ensure that our current backup solution is mentioned on https://gitlab.suse.de/suse/wiki/-/blob/main/qe_infrastructure.md

Because it's considered unreliable. Lemme rephrase the AC's, though.

Actions #5

Updated by livdywan 7 days ago

  • Subject changed from Follow-up steps regarding backup.qa.suse.de to Follow-up steps regarding backup.qa.suse.de (and backup.qe.prg2.suse.org)
  • Description updated (diff)
Actions

Also available in: Atom PDF