Project

General

Profile

action #113189

coordination #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

Research where we need limits size:S

Added by okurz about 1 month ago. Updated 28 days ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Feature requests
Target version:
Start date:
2022-07-04
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Acceptance criteria

  • AC1: We have a list of routes that do not yet have an upper limit

Suggestions

Walk over all defined routes in WebAPI.pm and check where we still need limits


Related issues

Related to openQA Project - action #114421: Add a limit where it makes sense after we have it for /tests, query configurableWorkable

History

#1 Updated by okurz about 1 month ago

  • Status changed from New to Workable

#2 Updated by mkittler 29 days ago

  • Status changed from Workable to In Progress
  • Assignee set to mkittler

#3 Updated by mkittler 29 days ago

  • Status changed from In Progress to Feedback

#5 Updated by mkittler 29 days ago

I've been creating a list, see the previous comment. This should be good enough for the sake of this ticket. We can now decide whether we want to put effort into improving any of those routes. Not sure whether it makes sense to create a ticket for each route. I suppose multiple routes can be updated in one go (without the change becoming too big).

#7 Updated by okurz 28 days ago

  • Status changed from Feedback to Resolved

Thx. This information makes sense. I created #114421, work here is done. But first we should do #111770 anyway

#8 Updated by okurz 27 days ago

  • Related to action #114421: Add a limit where it makes sense after we have it for /tests, query configurable added

Also available in: Atom PDF