On Mon, 2009-12-21 at 11:29 +1100, Michael Neale wrote:
On Thu, Dec 17, 2009 at 11:54 AM, David Lutterkort lutter@redhat.com wrote:
In concrete terms, it seems pretty clear how to describe a HWP: each dimension in a HWP is either a scalar range, with a unit, min and max bounds and an optional default value, or an enumeration of opaque strings, so that a HWP is a dictionary that maps the name of the dimension to a scalar range or an enumeration.
I think there is a case where you don't have either a range or enumeration of opaque strings, but you might have an enumeration of numeric/meaningful values, which a portal/client can use to decide what to use (eg how ec2 works now, effectively). I wouldn't want it to be either extreme only.
I didn't mean that as an either .. or .., even though I used those words - this was an inclusive or ;) As to whether the values of an enumeration are opaque or not is slightly different, in that it doesn't affect what a HW profile looks like; it's additional metadata about the grammar for HW profiles (which for now might only be in some docs)
David