Will 'openlmi-storage' follow the SNIA SMI-S standard?

Jan Safranek jsafrane at redhat.com
Thu Oct 31 08:07:40 UTC 2013


On 10/28/2013 01:58 AM, Gris Ge wrote:
> On Fri, Oct 25, 2013 at 05:05:46PM +0530, Devchandra L Meetei wrote:
>>>>>>>
>> If so, these two could be a good start:
>>  * DMTF DSP1033 Profile Registration
>>>>>>>
>> pegasus also has already implemented this so as stop repeat work from
>> different groups writing provider, so you can start using right away.
>>
> 
> I was expecting DSP1033 could help me jump 'root/interop' or 'interop'
> to OpenLMI 'root/cimv2' and provide me the tree-root 'CIM_ComputerSystem' for
> SNIA SIM-S 'Block Services' Profile.
> 
> I has not CIM provider experience or pegasus, but from a SMIS client view, this
> is how I understand the DSP1033.
> 
> Expected Way: [1]
>  * EnumerateInstances('CIM_RegisteredProfile') in 'interop' namespace.
>    # As DSP1033 state, 'root/interop' is OK while 'interop' is preferred.
>  * Find a profile with RegisteredName == 'Block Services'

This step won't work, we can't claim to implement  'Block Services'
profile, we don't implement Primordial Pool and maybe also other
mandatory classes. I could add a fake one, which would be read-only, but
isn't it against SMI-S?


Jan


More information about the openlmi-devel mailing list