Bug 1042163 - [RFE][heat]: Delete a stack without deleting the resources
Summary: [RFE][heat]: Delete a stack without deleting the resources
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-heat
Version: unspecified
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: ga
: 5.0 (RHEL 7)
Assignee: RHOS Maint
QA Contact:
URL: https://blueprints.launchpad.net/heat...
Whiteboard: upstream_milestone_icehouse-2 upstrea...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-12 21:14 UTC by RHOS Integration
Modified: 2014-09-08 05:42 UTC (History)
6 users (show)

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.
Clone Of:
Environment:
Last Closed: 2014-07-22 19:09:00 UTC
Target Upstream Version:


Attachments (Terms of Use)

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).


Note You need to log in before you can comment on or make changes to this bug.