[IMPROVEMENT] Consider disk space when creating BackingImage. Plus monitoring the disk usage of the BackingImage
ChanYiLin opened this issue · comments
Is your improvement request related to a feature? Please describe (👍 if you like this request)
Consider disk space
BackingImage can be created from: upload, download, export-from-volume, restore andclone
Currently we randomly choose one ready node and disk for the first BackingImage.
In some case, we won't be able to know the size of the BackingImage
In some case, we might have chance to know the size beforehand.
No matter what, we should always choose the disk with the largest space for the BackingImage.
If that disk is not enough for the BackingImage, at least we know there is no other disk enough.
Monitor the disk space usage
BackingImage is stored on the disks, we should monitor and present the space usage information to the user to increase the transparency.
Describe the solution you'd like
.
Describe alternatives you've considered
.
Additional context
.
Duplicated.