Project

General

Profile

Actions

action #101376

open

coordination #103941: [saga][epic] Scale up: Efficient, event-based handling of storage on new, clean instances

coordination #64881: [epic] Reconsider triggering cleanup jobs

Use cleanup triggers on finished jobs by default

Added by livdywan over 2 years ago. Updated over 2 years ago.

Status:
New
Priority:
Low
Assignee:
-
Category:
Feature requests
Target version:
Start date:
2021-08-31
Due date:
% Done:

0%

Estimated time:

Description

Motivation

#97763 implemented triggers on finished jobs via minion_task_triggers/on_job_done=. This would be great to enable by default, especially since currently no clean-up will ever be performed by default.

Acceptance criteria

  • AC1: Use cleanup triggers on finished jobs by default

Suggestions

  • Consider removing the dependency on the systemd timer and ensure that production instances still run cleanup after the update
    • Research how to properly communicate these changes based on systemd files, if no better way is found, just do it and tell our usual users, e.g. ping in pull request -> #101602
  • Get familiar with timers and triggers
  • Test the impact on performance, e.g. trigger 1k tiny jobs which trigger cleanup on done
  • Ensure that the df-check is enabled along with enabling the config
  • Add a default config for minion_task_triggers/on_job_done= in etc/openqa/openqa.ini (not in code so that existing instances are not changed)
  • Ensure that the configured cleanup jobs cover the same as the existing systemd timer

Related issues 1 (1 open0 closed)

Copied to openQA Project - action #101602: Research how to properly communicate these changes based on systemd files size:SWorkable

Actions
Actions

Also available in: Atom PDF