action #111770
closedcoordination #80142: [saga][epic] Scale out: Redundant/load-balancing deployments of openQA, easy containers, containers on kubernetes
coordination #92854: [epic] limit overload of openQA webUI by heavy requests
action #97190: Limit size of initial requests everywhere, e.g. /, /tests, etc., over webUI and API
Limit finished tests on /tests, but query configurable and show complete number of jobs size:S
Description
Acceptance criteria¶
- AC1: The number of finished tests on /tests is configurable by the user (with query parameter
limit), but limited server-side - AC2: By default we still show up to 500 finished jobs
Suggestions¶
- Look into what we recently did for the /tests/overview page where we also added an alert box if results are limited to 500, https://github.com/os-autoinst/openQA/blob/master/lib/OpenQA/WebAPI/Controller/Test.pm#L55
- Ensure there is a query parameter available to users to configure the number of results
- Ensure there is a server-side limit
- Add help text on the web UI (or documentation)
- Optional: UI elements to configure the limit directly
Out of scope¶
- Anything regarding direct use of the API, this is only about web UI
- This is only about "finished" tests. "scheduled" and "running" to be handled in parent epic
Updated by okurz over 2 years ago
- Subject changed from Limit all displayed tests on /tests, but query configurable and show complete number of jobs to Limit finished tests on /tests, but query configurable and show complete number of jobs size:S
- Description updated (diff)
- Status changed from New to Workable
- Target version changed from future to Ready
Updated by okurz over 2 years ago
- Copied to action #114421: Add a limit where it makes sense after we have it for /tests, query configurable size:M added
Updated by mkittler over 2 years ago
- Status changed from Workable to In Progress
Updated by mkittler over 2 years ago
- Status changed from In Progress to Feedback
The PR has been merged
Updated by kraih over 2 years ago
Is there an indicator telling the user that the number of results has been limited? With a new limited that's configured on the server side, it could be surprising to the user otherwise.
Updated by mkittler over 2 years ago
- Status changed from Feedback to Resolved
It says "Last X jobs" anyways. That a limit specified via a query parameter is clamped should therefore be apparent (and hopefully also not surprise anyone).
The change has been deployed on OSD and it works. Both ACs are fulfilled so I'm setting the ticket to resolved.
Updated by okurz about 2 years ago
- Status changed from Resolved to Feedback
The feature works as expected, e.g. https://openqa.opensuse.org/tests?limit=100000&match=krypton-live goes back 4 years. But I couldn't find any hint on the webUI how users would be able to do this, see the suggestion "Add help text on the web UI (or documentation); Optional: UI elements to configure the limit directly"
Updated by mkittler about 2 years ago
PR for help: https://github.com/os-autoinst/openQA/pull/4832
Updated by mkittler about 2 years ago
- Status changed from Feedback to Resolved
The PR has been merged.