Closed Bug 939886 Opened 11 years ago Closed 7 years ago

locking/rate limiting for slaveapi actions

Categories

(Release Engineering :: General, defect)

Product:
Release Engineering
Component:
General
Platform:
x86_64
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: bhearsum, Unassigned)

References

Details

(Whiteboard: [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/2796] [slaveapi])

Some actions in slaveapi can only be run one at a time safely. Some don't make sense to run more than once. There's a whole bunch of different things we could do here...including: * Only allow one action of any type at a time on any given slave. * Per-action limits on how many of that type can be run on a single slave at a time. * When a limit is hit, actions could be queued up, or rejected outright. * Some actions could be incompatible with other actinos. It's hard to foresee all of the use cases, so I don't think we should enforce any global limits - everything should be configurable per-action.
Depends on: 952264
Whiteboard: [slaveapi] → [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/2785] [slaveapi]
Whiteboard: [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/2785] [slaveapi] → [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/2794] [slaveapi]
Whiteboard: [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/2794] [slaveapi] → [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/2796] [slaveapi]
Component: Tools → General
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.