Hi Jan
Rechecked by registering the file you have mentioned.
Now I tend to believe that lmi exposes the profile with PG_ProviderProfileCapabilities. Or am I still missing due to a setup issue on my sys
If so, then won't it lead to some ambiguity as DMTF way is CIM_RegisteredProfile.
Also DMTF compliant Client application will not be able to discovery and inventory if so.
And as mentioned earlier,
Lmi seems to treat some CIMName as case sensitive which is a deviation from standard
Thanks Jan for the pointer.We used the CentOS-7 shipped openlmi. We don't build it.
Let me checkOn Tue, Feb 10, 2015 at 10:04 PM, Jan Safranek <jsafrane@redhat.com> wrote:On 02/10/2015 05:04 PM, Devchandra L Meetei wrote:
> Hi All
>
> Does openlmi providers advertise the CIM_registeredProfile for openlmi
> providers?
Yes, we do.
> I am not able to get it, prima facie, by a enumerate instance on interop
> namespace(both root/PG_InterOp and root/interop).
>
> It shows registeredProfiles of pegasus only.
There must be something wrong. Our packages in Fedora ship the profile
registrations and it registers them during package installation.
On my F21 system with random selection of OpenLMI providers I see 29
instances of PG_RegisteredProfile, many of them OpenLMI ones.
Check, if you have appropriate mof files (e.g.
/usr/share/openlmi-providers/90_LMI_Hardware_Profile.mof from
openlmi-hardware*.rpm or
/usr/share/openlmi-storage/70_LMI_Storage-Profiles.mof from
openlmi-storage*.rpm).
Of course, if you build from sources, I think you are on our own. You
can find the mof files in the source tree and register it manually.
Jan
_______________________________________________
openlmi-devel mailing list
openlmi-devel@lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/openlmi-devel
--Warm Regards
--Dev
OpenPegasus Developer
"I'm one of those people that think Thomas Edison and the light bulb changed the world more than Karl Marx ever did,” Steve Jobs