Hardware Profile Properties do not distinguish, values that determine, nothing,
everything, something
-----------------------------------------------------------------------------------------------------
Key: DTACLOUD-10
URL: https://issues.apache.org/jira/browse/DTACLOUD-10
Project: DeltaCloud
Issue Type: Bug
Reporter: Martyn Taylor
Assignee: David Lutterkort
At present HWP's can contain nil values for each of its cpu, memory, storage
and architecture fields.
This can be seen when using the MockDriver, in the Opaque HWP. In this case
nil means that this HWP does not offer anything in this HWP Property i.e. CPU,
mem etc....
In addition, GoGrid does not allow us to specify the architecture for of its
HWP. but it will give you an instance of some arbitrary architecture at
runtime. This case is also currently represented as 'nil'.
Using nil in this was causes ambiguity, In the two cases above, nil in one
sense means "we offer nothing", nil in another means "we offer something, but
what we offer is not specified"
There needs to be some way to determine the difference between the two cases:
A proposed solution to this problem, is to add an extra 'enum' value to the
'kind' field of the HWP Property Object, This can be used to represent an
'unspecified' value, as in the GoGrid case above. nil can then continue to be
used as representing "offer nothing" as in the MockDriver case.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
