On Wed, May 02, 2012 at 11:45:35AM +0100, Martyn Taylor wrote:
On 05/01/2012 07:41 PM, Matt Wagner wrote:
>While we have encouraged the use of "nil" to mean "No storage,"
some
>providers may report 0 GB. Currently, the code rejects this as invalid.
>Instead, we should treat this as valid. We still do not allow 0 for
>memory or CPU count, since those would not result in a system that
>can run -- but a system with no local storage may still be valid.
>---
<snip>
We should feed these types of inconsistencies back to deltacloud.
It's possible that nil and 0GB mean different things, though I
suspect really that these values should be transformed in DC Core.
After a lot of discussion* in #aeolus with Conductor and Deltacloud
folks, we concluded that 0 should indeed be a valid value for storage,
to expressly indicate that there is no storage. This patch implements
that, if anyone is able to review.
-- Matt
* Literally a conversation about nothing -- nil vs. 0.