Provider registration updates

Jan Safranek jsafrane at redhat.com
Tue May 14 08:57:04 UTC 2013


Hi,

I'm looking at how storage and software providers are registered into
SFCB and Pegasus and currently they will share their process under
sfcbd, which is quite unfortunate.

I'll use field 'group' in .reg files:
1) to make sure that these two providers runs in two processes under sfcbd.
2) as PG_ProviderModule.ProviderModuleName to show something better than
pyCmpiProvider.

Suggested format of this field is the RPM (sub)package name, i.e.:

group: openlmi-storage

This yields into:

instance of PG_ProviderModule
{
    Name = "openlmi-storage";
    Location = "pyCmpiProvider";
    Modulegroup = "openlmi-storage";
...
};

instance of PG_Provider
{
    Name =
"/usr/lib/python2.7/site-packages/openlmi/storage/cimom_entry.py";
    ProviderModuleName = "openlmi-storage";
};

instance of PG_ProviderCapabilities
{
   ProviderModuleName = "openlmi-storage";
   ProviderName =
"/usr/lib/python2.7/site-packages/openlmi/storage/cimom_entry.py";
   CapabilityID = "LMI_StorageExtent";
   ClassName = "LMI_StorageExtent";
...
};

I'll update openlmi-register-pegasus shortly. Other providers are
welcome to use this field to have nicer ProviderModuleName, but the
functionality of existing .reg files should remain consistent.

Jan


More information about the openlmi-devel mailing list