Heat abandon/adopt and alternatives
Bug #1791677 reported by
Tobias Rydberg
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Public Cloud WG |
Confirmed
|
Undecided
|
Tobias Rydberg | ||
Bug Description
It's sometimes necessary to delete all resources of a Heat stack except specific ones (like Cinder volumes that need preserving). Currently, there is no "good" way for doing that. openstack stack abandon is optional for providers to support, so may not be available in a public Heat service. What's do developers suggest is the preferred way for doing this? Manually take a snapshot of the volume that needs preserving, and then creating a new volume that is initialized from that snapshot?
Or else, are there plans to fix up abandon/adopt so that it's always available?
| Changed in openstack-publiccloud-wg: | |
| status: | New → Confirmed |
Revision history for this message
| Zane Bitter (zaneb) wrote | #1 |
Revision history for this message
| Florian Haas (fghaas) wrote | #2 |
To post a comment you must log in.
You can set the deletion_policy for a resource to 'retain'. (If you forgot to do that at the start, you can update the stack to include that in the template and as long as there are no other changes it won't affect anything.) For any resources with a deletion_policy of 'retain', the physical resource will be left in place but unmanaged by Heat when the resource (or indeed the entire stack) is deleted.
https:/