How To Find Out if CIM/WBEM packages provide SMI-S Compliant client APIs

[Anukalp Desai]

Hi all,

How could I find out if various CIM/WBEM packages like OpenPeagasus, SBLIM, pyWBEM are SMI-S Compliant
and do they provide SMI-S compliant client APIs.

If a CIM/WBEM package is not providing SMI-S compliant client APIs to use is there a way to include the support
for it?

WS SDK provides support for SMI-S so it must also provide SMI-S Compliant client APIs but I couldn't find
information about other CIM/WBEM packages.

[Peter Lamanna]

Hi Anukalp,

 

They are all WBEM Servers and Clients.  There is nothing SMI-S related to them per say.  That only happens when they host a provider that implements an SMI-S Profile.  Whether that implementation is officially compliant or not is done through the SNIA SMI-S Conformance Test Program (CTP).

 

Correct, the WSI SDK has the JSR48 interface and not anything SMI-S specific.  If you are looking for a programming interface a level or two up from that it would have to be a client implementation that is written against SMI-S profiles.  One example of this type of interface is the Windows Storage Management API.

 

I hope this helps.

 

Regards,

Peter

--
You received this message because you are subscribed to the Google Groups "SMI-S Developers Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to smi-s-developers-...@googlegroups.com.
To post to this group, send email to smi-s-devel...@googlegroups.com.
Visit this group at http://groups.google.com/group/smi-s-developers-group.
For more options, visit https://groups.google.com/d/optout.

[Anukalp Desai]

Hi Peter,

Thanks for your reply!

So a management application can use any of these WBEM/CIM Clients APIs and can manage a SAN resource irrespective of whether that resource is
implementing SMI-S profiles or not. The management application can find out which profiles(CMI, SNIA SMI-S) are implemented by the provider through WBEM
server and can work with those profiles. Am I correct?

I am trying to understand whether using the WBEM/CIM Clients APIs a management tool can findout which profiles are implement for a SAN resource
(specifically SMI-S profiles) and then work with those SMI-S profiles or whether a WBEM/CIM client has to be specially written against SMI-S profile by extending
the existing WBEM/CIM Clients so that a SMI-S compliant SAN resource could be managed by it.

[Gris Ge]

On Sat, Mar 08, 2014 at 06:26:36AM -0800, Anukalp Desai wrote:
> Hi Peter,
>
> Thanks for the reply!
>
> Could a management tool, using any of the WBEM/CIM Client APIs find
> out which SMI S profiles have been implemented and then use those to
> manage the SAN resource or does a WBEM/CIM client has be to
> specifically written against SMI-S profile so that it could provide
> APIs for managing a SAN resource that is SMI-S compliant.
>
>

Hi Anukalp Desai,

You can use DMTF Standard DSP1033 "Profile Registration"[1] to find out
what profile and which version is supported by current SMI-S provider.

Quick view:

1. Enumerate CIM_RegisteredProfile in 'interop' or 'root/interop'
namespace.
2. CIM_RegisteredProfile['RegisteredName'] is the name of profile.
CIM_RegisteredProfile['RegisteredVersion'] is the version of
profile supported.
CIM_RegisteredProfile['RegisteredOrganization'] should be
11(SNIA).
3. Let's assume you need SNIA SMI-S 'Block Services Package' 1.6
version.
4. We find one CIM_RegisteredProfile meet the requirements.
5. By checking SNIA SMI-S 1.6 spec, 'Block Services Package' is a
sub profile of 'Array' profile.
6. You have two way to find out the 'Array' profile:
A: Use 'CIM_ReferencedProfile' association recursively tile found
the root profile.
B: Find 'Array' profile with the same version number of the
found 'Block Services Package' from the enumerated
CIM_RegisteredProfile list.
I chose the B)
7. Use this association to get the root CIM_ComputerSystem.

CIM_RegisteredProfile # interop namespace
|
| CIM_ElementConformsToProfile
|
v
CIM_ComputerSystem # vendor implementation namespace
8. Follow whatever association 'Block Services Package' defined to
meet your needs.

If LGPL copyright does not bother you, this is my patch(using pywbem)
to support profile registration:
http://sourceforge.net/p/libstoragemgmt/mailman/message/31992983/

Hope that helps.
Best regards.

[1] http://www.dmtf.org/standards/search?keys=&dsp=1033&tid=All
--
Gris Ge

[Anukalp Desai]

Thanks Gris and Peter!

Your posts answered my questions.