| |
|
 |
|
 |
|
|
|
| |
|
|
xen-cim
[Xen-cim] CMPI support of arrays in OUT params
> It appears CMPI (1.3 or 2.0) does not support extrinsic method OUT params
that
> are arrays. For the VirtualSystemManagementService provider, arrays of
> references are problematic. AddResourceSettings() and
ModifyResourceSettings()
> both have OUT params that are reference arrays. OpenWBEM does not
support this
> - segfaults when calling something like:
>
> CMAddArg(argsout, "OutSettings", (CMPIValue*)&array, CMPI_refA);
>
> I have not tried Pegasus but would expect the same -- well, hopefully it
fails
> more gracefully :-).
>
> I do not plan to support AddResourceSettings, ModifyResourceSettings and
> RemoveResourceSettings in CIM_VirtualSystemManagementService and instead
> support AddResourceSetting, ModifyResourceSetting and
RemoveResourceSetting
> (notice the singular setting) in our derived management service class. A
> single reference will be returned in these versions, side-stepping the
above
> issue.
>
> Frankly, the plural versions suck anyway :-). I came to this conclusion
while
> implementing AddResourceSettings. Implementation is difficult,
particularly
> handling errors. Imagine successfully adding 2 resources but failing on
the
> 3rd. Do you fail the whole thing and attempt to unwind (and perhaps fail
doing
> that!)? Or do you proceed forward and indicate half failure? I don't
like it
> and considered the 'one-at-a-time' approach before hitting the 'output
array' >
> issue.
>
> I will proceed with this approach unless (strongly) convinced otherwise.
>
> Jim
Jim,
in DMTF SVPC we modelled that way
to enable the client to pass in multiple
logically related requests in one step,
that either succeeds or fails as a whole.
Admittedly that makes things more difficult
for the implementation, but consider that
with the single step approach you leave
the responsiblity for cleanup to the client,
and if he does not care about that responsibility,
then you end up with inconsistent system definitions.
Of course the issue with cmpi needs to be addressed.
Michael
_______________________________________________
Xen-cim mailing list
Xen-cim@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-cim
|
|
|
| |
|
Home