action #88546
closed
openQA Project (public) - coordination #64746: [saga][epic] Scale up: Efficient handling of large storage to be able to run current tests efficiently but keep big archives of old results
openQA Project (public) - coordination #80546: [epic] Scale up: Enable to store more results
Make use of the new "Storage Server", e.g. complete OSD backup
Added by okurz almost 4 years ago.
Updated about 3 years ago.
Description
Acceptance criteria¶
- AC1: The SUSE QA storage server is used within our production and we (the team) know what is used for
Suggestions¶
Ask nsinger where to connect to, what steps to start with? The hostname is storage.qa.suse.deTry to connect to storage.qa with the same credentials as for osd machines maintained with salt, e.g. just ssh with your user should work SSH access should work at this point- Add changes and make sure the changes are in salt
- When populating the
btrfs filesystem storage.qa.suse.de:/storage it would make sense to create dedicated subvolumes for different things
- e.g. do a full or partial backup of OSD
- e.g. mount storage.qa.suse.de:/storage on OSD and configure the archiving feature to use it
- What is included in a complete OSD backup?: To be answered by #96269
- Also include postgres? okurz: No, to be covered by #94015
- Which backups solution to use, e.g. rsnapshot?: okurz: Yes, use rsnapshot, same as we currently do on backup.qa.suse.de already
Further details¶
If we try to conduct a "complete OSD backup" by this we can also learn the performance impact, e.g. how long does it initially take to synchronize, how long does it take to do individual, e.g. daily syncs
- Copied from action #69577: Handle installation of the new "Storage Server" added
Could we add some suggestions here and make it Workable? Like where to connect to, what steps to start with?
- Description updated (diff)
- Status changed from New to Workable
Yes, we should. I can't do much on that on my own though. nsinger knows more
- Description updated (diff)
- Description updated (diff)
- Description updated (diff)
Now with the archiving feature enabled one could try to mount storage.qa.suse.de:/storage on OSD and configure the archiving feature to use it.
- Related to action #92701: backup of etc/ from both o3 was not working since some days due to OOM on backup.qa.suse.de (was: … and osd not updated anymore since 2019) added
- Description updated (diff)
I've been updating the ticket description:
- There's an overlap between this ticket and #92701. I suppose if we opt for the full backup of OSD here we wouldn't need #92701 anymore. It also leads to the idea of only backing up
/etc (and maybe some other important directories) first.
- It looks like
/storage on storage.qa.suse.de is using btrfs. That makes sense and I suppose if we populate it with various things, e.g. an archive or backups we should create an own subvolume for these.
- Status changed from Workable to In Progress
- Assignee set to mkittler
Now since we have the archiving feature enabling it is likely the easiest use of the storage server so I'll start with that.
- Due date set to 2021-06-16
Setting due date based on mean cycle time of SUSE QE Tools
before we accept the MR we should do #91779 first. Also see the problem of this morning about storage.qa: #93683
- Status changed from In Progress to Workable
- Assignee deleted (
mkittler)
I haven't progressed here since we decided to focus on #92701 first. I'm unassigning because I won't be able to work on this until next Tuesday.
- Due date deleted (
2021-06-16)
- Status changed from Workable to New
moving all tickets without size confirmation by the team back to "New". The team should move the tickets back after estimating and agreeing on a consistent size
- Blocks action #92788: Use openQA archiving feature on osd size:S added
- Description updated (diff)
We need to answer the two last questions in suggestions section before do it workable
- Copied to action #96269: Define what a "complete OSD backup" should or can include added
- Description updated (diff)
- Related to action #44078: Implement proper backups for o3 size:M added
- Status changed from New to Blocked
- Assignee set to okurz
- Status changed from Blocked to Resolved
With #44078 completed we make active use of the storage space on storage.qa.suse.de and also that host is fully controlled with salt and actively monitored. Team agreed that we have AC1 covered :)
Also available in: Atom
PDF