[occi-wg] occi.compute.speed

[alexander.papaspyrou at tu-dortmund.de]

Folks,

in our implementation efforts of building an OCCI service frontend to libvirt, Sebastian and Ediz had a problem in supporting the "occi.compute.speed" attribute towards the libvirt backend -- there seems to be no way of setting this.

Glancing at the libvirt docs, I couldn't find explicit support for this either. The question is: am I too stupid, and --- if not --- shall we change the multiplicity of "occi.compute.speed" from "1" to "0..1", since the speed might not be supported everywhere.

Another thing that came up to my mind is: how shall we cope with this in the implementation via HTTP: if I POST a new compute, with a speed attribute set, and the backend builds upon libvirt (effectively not supporting it), can I give back a 20* status code and create _some_ resource (and corresponding VM), or is this a bad request?

It also seems to me that this special case is something that makes resource templates important -- are we moving into the right direction here?

Best,
Alexander