Project

General

Profile

coordination #92323

[saga][epic] Scale up: Fine-grained control over use and removal of results, assets, test data

Added by okurz 3 months ago. Updated 3 months ago.

Status:
New
Priority:
Low
Assignee:
-
Category:
Feature requests
Target version:
Start date:
2020-05-20
Due date:
% Done:

0%

Estimated time:
(Total: 0.00 h)
Difficulty:

Description

Ideas

  • Have a configurable list of file type/name/pattern with retention period or size quota for each file type/name/pattern
  • Allow to configure retention period for the video individually #67087
  • Something better than single fixed, unflexible volumes. E.g. dm-cache, lvmcache, bcache, SUSE enterprise storage. Maybe also splitting stored results in openQA by "recent, active" and "old, archived" and then put both categories in different folders which can be mounted from different storage locations, e.g. fast, expensive for "recent, active" and slow, cheap, big for "old, archived"
  • try out tuned ext4 for worker pool fs to use a more modern default base fs than ext2 even though internally it's the same new code but we might benefit still, e.g. from faster fs formatting times. #64746#note-2

Subtasks

action #67087: Allow to configure retention period for the video individuallyNew

openQA Infrastructure - action #77845: Use external videoencoder in production on all osd machinesNew

openQA Infrastructure - action #77848: No more workarounds in OSD due to inefficient video encoderNew


Related issues

Copied from openQA Project - 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 resultsBlocked2020-03-182021-08-31

History

#1 Updated by okurz 3 months ago

  • Copied from 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 added

Also available in: Atom PDF