Comment 6 for bug 1878024
Revision history for this message
| Balazs Gibizer (balazs-gibizer) wrote | #6 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
Dan refined the idea of Option A) [1]:
1. Each time we cache an image, or run the periodic, we generate a disk allocation for the compute node uuid which consumes inventory according to how much space the cache is using
2. Same as above, but adjust the reserved amount.
Both cases need to consider the case where the _base is not on the same filesystem as the instances, but there's less synchronization involved, and we're not spraying tons of new allocations into place we could also make it a workaround that you opt into in the short term to see how it goes, because cleanup from it would be much easier (just nuke one $cnuuid allocation) and we could make compute node startup nuke that allocation if present and the workaround is disabled (or the self-correcting reserved amount)
Glance API provides the physical size of the image so nova-compute can try to allocate / reserve that amount of DISK_GB resource in placement _before_ download the image to the cache.
[1] http://