Deleting VMs shouldn't count against quota
Bug #1026237 reported by
Phil Day
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Compute (nova) |
Invalid
|
Undecided
|
tgalvin | ||
Bug Description
As the only thing a user can do once an instance enters the "deleting" state (which is does in the API) is to request to delete it again it should be excluded from quota calculations.
The issus here is if a compute node is down (which may be why the user is doing the delete) the delete itslef may take soem time to process. This is generally the service providers problem not the users, and so they should be allowed to start a replacement VM.
Suggest that this behaviour is controlled by a flag so that it can be configured either way.
| Changed in nova: | |
| assignee: | nobody → tgalvin (tom-galvin) |
Revision history for this message
| Phil Day (philip-day) wrote | #1 |
| Changed in nova: | |
| status: | New → Invalid |
Revision history for this message
| Andrea Frittoli (andrea-frittoli) wrote | #2 |
To post a comment you must log in.
I want to withdraw this as a bug - i tlooks like the quota refactoring has addressed this already.