No size restrictions in place for Images and Kernels

Hi! What would you propose would be a size limit? Or should it be configurable? Configurable by backend? In other words, filesystem backend could be different size limit from Swift backend?

In order to be flexible, the size limit should be configurable. The main idea is to protect the hypervisor and prevent situations where large kernels or images were registered on purpose to cause host issues. For example, XenServer only provides 4GB for dom0. For builds with kernels outside of the instance, they are stored on the dom0 filesystem in /boot/guest and at a certain point could fill up the filesystem if not kept in check.

In talking with Rick Harris it would probably be set at the compute layer, either a limit per image or file, or an overall filesystem percentage free space check.

OK, thx Ant! Moving to the Nova project, as Rick says, better to do the limiting at the compute layer.

Setting as High due to potential security implications