| 2018-03-24 03:14:19 |
yangjie |
description |
The value of disk_available_least become negative unexpectedly, because we allow to boot a image-based vm using a flavor with 0 GB disk size.
When user try to boot a image-based vm using a flavor with 0 GB disk size, Nova use the virtual size from image property to replace the '0' size to create disk file in instance folder.
This virtual size from image property make the value of disk_available_least inconsistent with flavor-based estimate. It makes user confused sometimes.
Maybe we should forbid the creation of a vm from a flavor with zero disk size, and throw out a HTTP exception in Nova API. |
The value of disk_available_least become negative unexpectedly, because we allow to boot a image-based vm using a flavor with 0 GB disk size.
When user try to boot a image-based vm using a flavor with 0 GB disk size, Nova use the virtual size from image property to replace the '0' size to create disk file in instance folder.
This virtual size from image property make the value of disk_available_least inconsistent with flavor-based estimate. It makes user confused sometimes.
Maybe we should forbid the creation of a image-based vm from flavor with zero disk size, and throw out a HTTP exception in Nova API. |
|
