Project

General

Profile

action #91782

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

coordination #80546: [epic] Scale up: Enable to store more results

Add support for archived jobs

Added by okurz 6 months ago. Updated 4 months ago.

Status:
Resolved
Priority:
Low
Assignee:
Category:
Feature requests
Target version:
Start date:
2021-04-26
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Motivation

See parent #80546 . To be able to scale-up openQA we want to be able to separate recent openQA results (on expensive+fast storage) from older, important openQA results (on slow+cheap storage).

Acceptance criteria

Suggestions

Out of scope

  • UI representation for archived jobs: #91785

Related issues

Related to openQA Project - coordination #76984: [epic] Automatically remove assets+results based on available free spaceNew2021-01-21

Copied to openQA Project - action #92788: Use openQA archiving feature on osd size:SBlocked

History

#1 Updated by okurz 6 months ago

  • Description updated (diff)

#2 Updated by okurz 6 months ago

  • Description updated (diff)

#3 Updated by mkittler 6 months ago

Since I've already started with https://github.com/os-autoinst/openQA/pull/3858 I'd also like to finish it. So I'll take the ticket when it is moved to the backlog.

#4 Updated by okurz 5 months ago

  • Target version changed from future to Ready

#5 Updated by mkittler 5 months ago

  • Assignee set to mkittler

#6 Updated by okurz 5 months ago

  • Due date set to 2021-05-25
  • Status changed from Workable to In Progress

#7 Updated by mkittler 5 months ago

  • Status changed from In Progress to Feedback

I'm waiting for PR reviews. See the commit message of the last commit for remaining caveats. For now I'd refrain from any complicated hacks to overcome them as they shouldn't be very problematic in practice.

#8 Updated by okurz 5 months ago

  • Related to coordination #76984: [epic] Automatically remove assets+results based on available free space added

#9 Updated by mkittler 5 months ago

  • Status changed from Feedback to Resolved

I'm closing the ticket despite the remaining caveats. The archiving job takes care to delete any leftovers if copying fails so if cleanup and archiving interfere with each other the worst which can happen is a failed archiving job (but leftovers should not pile up in the archive). Besides, this is very unlikely anyways.

#10 Updated by okurz 5 months ago

  • Copied to action #92788: Use openQA archiving feature on osd size:S added

#11 Updated by cdywan 4 months ago

  • Due date deleted (2021-05-25)

Also available in: Atom PDF