I sent this last week but got no response, and it's now lost in the noise, so I've
rebased and am now resending. From my original posting:
Wes hit a bug with Hardware Profile matching. It turns out that
HardwareProfile.generate_override_property_values was returning the front-end value for
HWPs if the provider value was a range. This meant that if you designed a front-end
profile with, say, nil CPUs (meaning "no prerefence"), and it matched onto a
provider HWP with a range (1-4 for VMware), we'd end up passing the "nil
CPUs" parameter to deltacloud when trying to start an instance.
This also adds a test case for this to try to keep us from having so many regressions
here.
-- Matt