Heat abandon/adopt and alternatives

[Tobias Rydberg]

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?

[Zane Bitter (zaneb)]

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://docs.openstack.org/heat/latest/template_guide/hot_spec.html#resources-section

[Florian Haas (fghaas)]

Excellent to know, thanks Zane! (I'm the one who put this issue into Tobias' Denver luggage. :) )