Resource Cleanup options at creation
Registered by
Michael Petersen
Certain resources may/may not need to be cleaned up at deletion of the environment. One example of this would be Floating IP addresses. Depending on the use case the end user could expect the Floating IP to be released back into the pool, or they could expect to keep the Floating IP address as they may configure DNS for it. There should be an option at creation to allow for different levels of cleanup based on the resources.
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Michael Petersen
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- New
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
The current upstream engine implementation relies on Heat provisioning engine. It means that Sahara uses Heat stacks to create and clean up resources.
So the functionality described here needs to be available in Heat in first place.
(?)
