Bug 1042163

Summary: [RFE][heat]: Delete a stack without deleting the resources
Product: Red Hat OpenStack Reporter: RHOS Integration <rhos-integ>
Component: openstack-heatAssignee: RHOS Maint <rhos-maint>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: medium Docs Contact:
Priority: low    
Version: unspecifiedCC: markmc, mlopes, sbaker, sdake, shardy, yeylon
Target Milestone: gaKeywords: FutureFeature
Target Release: 5.0 (RHEL 7)   
Hardware: Unspecified   
OS: Unspecified   
URL: https://blueprints.launchpad.net/heat/+spec/abandon-stack
Whiteboard: upstream_milestone_icehouse-2 upstream_status_implemented upstream_definition_approved
Fixed In Version: Doc Type: Enhancement
Doc Text:
With this enhancement, users are able to abandon a stack in Orchestration and still retain the stack resources. As a result, stack resources remain after a stack abandon operation.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2014-07-22 19:09:00 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description RHOS Integration 2013-12-12 21:14:49 UTC 
Cloned from launchpad blueprint https://blueprints.launchpad.net/heat/+spec/abandon-stack.

Description:

This blueprint is partnered with blueprint adopt-stack to allow stacks to be moved from one heat instance to another in a 2 step process:
* a stack is abandoned, deleting the stack but leaving the resources running
* the state returned from the abandon action is used to do a stack adopt. This creates a stack which adopts the passed resources, and does not create any new resources

This blueprint may be useful on its own for users who want to use heat to use heat to invoke openstack resources but don't want to use heat to manage those resources.

Abandoning a stack would do the following:
* Collect all the resource state (resource IDs, resource data, metadata?)
* Delete the stack with DeletionPolicy on all resources overridden to 'Retain'
* Return a json structure to the user containing the abandoned template, plus the resource state

The json structure will be in a format that can be consumed by blueprint adopt-stack

Specification URL (additional information):

None
Comment 2 Stephen Gordon 2014-01-23 20:51:08 UTC 
Moving to POST based on upstream status (Implemented).