Thanks for comments @demobox Agree don't like breaking backwards compatibility for those wanted 16GB not getting the smallest, but feels like the right thing moving forwards. I could add a warning if the value is less than 100 or something like that (but haven't seen that pattern in other jclouds places)?
If user requests 1536MB... when we're collecting the "pricing info" for hardware profiles, getting back 8 and 16, we'll convert those to 1*1024 and 2*1024 for the actual `Hardware` instance. The `TemplateBuilderImpl.hardwareRamPredicate` will do `2048 > 1536` to return true as an acceptable hardware profile. So I think that's fine. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/147#issuecomment-24241277
