action #91782

Updated by okurz 5 months ago

## 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
* **AC1:** results on openQA can be automatically separated into two different storage targets
* **AC2:** is merged or closed

## Suggestions
* Add help in web UI based on describing the impact of periods selected for "important" jobs when archiving is enabled
* Add comments in the example openqa.ini describing the archiving feature based on
* Add documentation for the new openQA feature based on where the internal help and the comments in openqa.ini seem not enough
* Run tests, e.g. in SUSE internal's staging setup
* Add a complete implementation of the draft - continue and finish it or start over :)

## Out of scope
* UI representation for archived jobs: #91785