allow suspend/resume of clusters
Bug #1745625 reported by
Ricardo Rocha
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Magnum |
New
|
Undecided
|
Unassigned | ||
Bug Description
It would be useful to allow suspend and resume of clusters, following the Heat functionality of stack suspend/resume.
We have a use case where when users leave the organization we first suspend all their resources (VMs, etc) and disable the user. Deletion only happens a while after this first step.
As it is today, the magnum periodic checks will keep trying to contact the cluster and failing as it can't resolve the user (account suspended). If after that it would still fail to contact the cluster as all VMs are suspended.
We likely need two new api calls and cli commands, and a new state SUSPENDED.
To post a comment you must log in.
