Clean up clusters that are in non-final state for a long time
Registered by
Andrew Lazarev
For now it is possible that sahara cluster becomes stuck because of different reasons (e.g. if sahara service was restarted during provisioning or neutron failed to assign floating IP). This could lead to clusters holding resources for a long time. This could happen in different tenants and it is hard to check such conditions manually.
Proposed solution: delete sahara cluster in non-final state if it wasn't updated for a long time.
Blueprint information
- Status:
- Complete
- Approver:
- Sergey Lukjanov
- Priority:
- High
- Drafter:
- Andrew Lazarev
- Direction:
- Approved
- Assignee:
- Andrew Lazarev
- Definition:
- Approved
- Series goal:
- Accepted for kilo
- Implementation:
-
Implemented
- Milestone target:
-
2015.1.0
- Started by
- Sergey Lukjanov
- Completed by
- Sergey Lukjanov
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Clean up clusters that are in non-final state for a log time
Addressed by: https:/
Added periodic clean up of old inactive clusters
(?)
