Backlog #2402
Keep track of allocated storage in DS
| Status: | Pending | Start date: | 10/23/2013 | |
|---|---|---|---|---|
| Priority: | High | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | Core & System | |||
| Target version: | - |
Description
The same way the hosts keep the allocated counters, the image and system DS could know the allocated storage for the running VMs.
This info can be used in the onevm deploy --enforce action.
Related issues
History
#1
Updated by Ruben S. Montero over 7 years ago
- Target version set to Release 4.6
#2
Updated by Ruben S. Montero over 7 years ago
- Tracker changed from Feature to Backlog
- Status changed from New to Pending
- Priority changed from Normal to High
- Target version deleted (
Release 4.6)
#3
Updated by Carlos Martín over 7 years ago
- Related to Backlog #2737: Consider Storage allocation USED vs ALLOCATED datastore capacity added
#4
Updated by Jaime Melis about 7 years ago
- Related to Bug #2783: Storage size calculation for Datastore using du added
#5
Updated by OpenNebula Systems Support Team almost 5 years ago
- Target version set to Release 5.4
In order to take into account the consumed space in the FS, the right approach would be to have the monitoring probes count the maximum space to which the sparse images can grow.
This needs to be evaluated to every possible configuration of datastores and sparse image formats.
#6
Updated by Ruben S. Montero over 4 years ago
- Target version deleted (
Release 5.4)