action #181151
opencoordination #161414: [epic] Improved salt based infrastructure management
Follow-up steps regarding backup.qa.suse.de (and backup.qe.prg2.suse.org)
0%
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¶
- Update https://gitlab.suse.de/suse/wiki/-/blob/main/qe_infrastructure.md
- See https://gitlab.suse.de/suse/wiki/-/commit/0e4317a19d736a50b136f80a8fb7d8c9b569a014 which says As of 2025-04-20 backup.qa.suse.de was replaced by backup.qe.prg2.suse.org.
- We should discuss this regardless since we don't seem to have consensus within the team
- Copy existing backups over to nfs-prg2-fas-prod.openplatform.suse.com
- Wait a couple days just in case?
- Delete backup.qa.suse.de - it's just a VM on qamaster
Updated by livdywan 12 days ago
- Copied from action #173674: qamaster-independent backup size:S added
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
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.