Bug #3467
UI proceeds with VM creation while not enough resources are available
| Status: | Assigned | Start date: | 03/21/2013 | |
|---|---|---|---|---|
| Priority: | High | Due date: | ||
| Assignee: | Kostas Papadimitriou | % Done: | 0% |
|
| Category: | Cyclades UI | Spent time: | - | |
| Target version: | 0.13.0 |
Description
Reported by kargig at okeanos-dev.
From listing the user's quota and usage,
the user does not have enough 'cyclades.vm',
but does have enough from all the others.
Maybe the UI does not check for 'cyclades.vm'?
History
#1 Updated by Kostas Papadimitriou about 11 years ago
When vm quota limit is reached ui disables the "Create machine" action.
UI updates the available user quotas in intervals of 10 seconds, so there is a time window (after the creation of the last available vm) when UI allows user to create a new VM but the quota limit has already been reached.
This can be solved if UI enforce quotas to be updated after each API creation/delete action.
#2 Updated by Vangelis Koukis about 11 years ago
- Status changed from New to Assigned
In a similar spirit:
There is no reason to be exact:
Whenever a new create operation is submitted, just compute the new quotas heuristically:
Reduce the quota values according to the VM creation parameters, in the in-memory data model, proactively.
The user will not be able to create a new VM immediately, without actually performing a GET /quotas, or similar call.
Then, after at most 10 seconds, the in-memory data will actually be updated with real data from GET /quotas.
But the UI will look great in between, without the overhead of extra calls.