[RFE] Handle Timeouts Generically

Bug #1526420 reported by Vladyslav Drok on 2015-12-15
4
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ironic
Confirmed
Wishlist
Unassigned

Bug Description

When a request is received via RPC, some work is started asynchronously by the Conductor process. At this time, there is no process watching to see how long that work has taken and potentially stop it after a configurable timeout.

Because drivers may implement their respective interfaces in different ways, we need a general way for the Conductor to ask the driver if an operation has taken "too long." The set of timeouts should be standardized across drivers. Individual timeouts should be configurable per-driver.

This also requires that drivers advertise which operations are interruptable, and a means to interrupt those that are.

Related to:
- https://bugs.launchpad.net/ironic/+bug/1526352
- https://blueprints.launchpad.net/ironic/+spec/abort-deployment

Vladyslav Drok (vdrok) on 2015-12-15
Changed in ironic:
status: New → Confirmed
importance: Undecided → Wishlist
tags: added: rfe

This will need a spec

tags: added: needs-spec
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Related blueprints