Comment 19 for bug 1029950

Eek this is a bit awkward. I'm not sure how to address this TBH, just some notes...

A related nova commit with inline comments on space checking is
https://review.openstack.org/#/c/11399/3

The issue would be mitigated somewhat if nova could always
do a HEAD first to get the image size, and check/preallocate that.
But Derek's point in comment 5 suggests that the GET
might in fact get more. In any case I suppose someone could
still start high and reduce the size until they got an image that
just filled the disk.

Having a max size per image would help, but not if
users could use many such images. That would have
to be enforced by quotas/billing.