Dependency-driven multi-step resource deallocation
Murano components may allocate various kinds of resources: virtual machines,
networks, volumes etc. When these components get removed from the deployment
appropriate resources have to be deallocated. Current implementation of this
process has some significant limitations and flaws.
This specification aims to address these issues and provide a design for the
better resource deallocation / garbage collection system for MuranoPL.
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- High
- Drafter:
- Alexander Tivelkov
- Direction:
- Approved
- Assignee:
- None
- Definition:
- Approved
- Series goal:
- Accepted for newton
- Implementation:
-
Implemented
- Milestone target:
- None
- Started by
- Nikolay Starodubtsev
- Completed by
- Nikolay Starodubtsev
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
An initial commit for MuranoPL garbage collector
Addressed by: https:/
Add tests for MuranoPL garbage collector
Gerrit topic: https:/
Gerrit topic: https:/
Addressed by: https:/
Break cyclic references in DSL
Addressed by: https:/
ObjectStore parent lookup with temporary id was fixed
Gerrit topic: https:/
Addressed by: https:/
Object's properties deserialize was fixed
Addressed by: https:/
Delete alternate DB migration branches
Addressed by: https:/
On-demand garbage collection
Addressed by: https:/
Raise exception on call of method of destroyed object
Addressed by: https:/
Pass receiver to :GC.subscribeDe
Addressed by: https:/
Serialization of destroyed objects
Addressed by: https:/
Serialization of destruction dependencies
Addressed by: https:/
GC.isDoomed() and GC.isDeleted() functions were added
Addressed by: https:/
Prevent executor finalization until exception are not handled
