Project

General

Profile

Actions

action #98922

closed

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 results

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

coordination #96974: [epic] Improve/reconsider thresholds for skipping cleanup

Run asset cleanup concurrently to results based on config

Added by mkittler almost 3 years ago. Updated over 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
-
Target version:
Start date:
2021-09-20
Due date:
% Done:

0%

Estimated time:

Description

motivation

see #96974

acceptance criteria

  • AC1: A configuration option exists to allow asset and result cleanup concurrently.

suggestions

  • Make the acquisition of the limit_tasks lock depended on a config value in limit tasks for assets and results.

Related issues 1 (0 open1 closed)

Copied to openQA Infrastructure - action #103954: Run asset cleanup concurrently to results based on config on o3 as wellResolvedokurz

Actions
Actions #1

Updated by mkittler almost 3 years ago

  • Status changed from New to In Progress
Actions #2

Updated by openqa_review almost 3 years ago

  • Due date set to 2021-10-05

Setting due date based on mean cycle time of SUSE QE Tools

Actions #3

Updated by mkittler almost 3 years ago

The PR hasn't been merged yet but I've already created the SR to use the configuration on OSD: https://gitlab.suse.de/openqa/salt-states-openqa/-/merge_requests/584

Actions #4

Updated by okurz almost 3 years ago

Both https://github.com/os-autoinst/openQA/pull/4215 and https://gitlab.suse.de/openqa/salt-states-openqa/-/merge_requests/584 merged. Next automatic deployment should pick it up on this Friday.

Actions #5

Updated by mkittler almost 3 years ago

  • Status changed from In Progress to Feedback
Actions #6

Updated by okurz over 2 years ago

  • Tracker changed from coordination to action
Actions #7

Updated by mkittler over 2 years ago

  • Status changed from Feedback to Resolved

I just triggered a cleanup job in production and had a look at the locks. Looks like it works.

Actions #8

Updated by okurz over 2 years ago

  • Due date deleted (2021-10-05)
Actions #9

Updated by okurz over 2 years ago

  • Copied to action #103954: Run asset cleanup concurrently to results based on config on o3 as well added
Actions

Also available in: Atom PDF