Checking for nested stack status is expensive
Bug #1549213 reported by
Thomas Herve
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Heat |
Fix Released
|
Medium
|
Thomas Herve | ||
Bug Description
When we create a nested stack, we poll the database for its status. But currently, to get the status we load the whole stack and its template, just for a few bits of information. We should optimize that.
| Changed in heat: | |
| status: | New → In Progress |
| Changed in heat: | |
| milestone: | mitaka-3 → mitaka-rc1 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to heat (master) | #1 |
| Changed in heat: | |
| status: | In Progress → Fix Released |
| tags: | added: liberty-backport-potential |
Revision history for this message
| Thierry Carrez (ttx) wrote Fix included in openstack/heat 6.0.0.0rc1 | #2 |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit b862908d4cdade7
Author: Thomas Herve <email address hidden>
Date: Fri Feb 12 12:14:12 2016 +0100
Optimize nested stack status check
Currently, StackResource loads the whole stack when checking for status
(in check_*_complete method), but only care about the state of the
stack. This is a fairly expensive operation, as it retrieves the
template and reparses everything. This simplifies it with a new API that
simply query the stack status from the database.
Closes-Bug: #1549213
Change-Id: I18df89a2b99592