Add configurable timeouts for SoftwareDeployment resources
Bug #1557764 reported by
Jay Dobies
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Heat |
In Progress
|
Wishlist
|
Jay Dobies |
Bug Description
Given the flexibility of what can be done with a SoftwareDeployment, it would be useful to be able to configure an individual timeout for them. That would let users be more strict than NO_SIGNAL but not have a stack remain *_IN_PROGRESS for potentially long periods of time.
Changed in heat: | |
importance: | Medium → Wishlist |
Changed in heat: | |
assignee: | nobody → Jay Dobies (jdob) |
description: | updated |
Changed in heat: | |
assignee: | Jay Dobies (jdob) → huangtianhua (huangtianhua) |
Changed in heat: | |
milestone: | newton-1 → newton-2 |
Changed in heat: | |
milestone: | newton-2 → newton-3 |
Changed in heat: | |
assignee: | Jay Dobies (jdob) → huangtianhua (huangtianhua) |
Changed in heat: | |
assignee: | huangtianhua (huangtianhua) → Jay Dobies (jdob) |
Changed in heat: | |
milestone: | newton-3 → next |
To post a comment you must log in.
Sounds good. +2 from me