[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-cim] Re: Interop namespace question



Szymanski, Lukasz K wrote:
Jim -

You suggested we try to
- Connect to cimom and look in Interop namespace for our profiles

I'm having trouble doing that on my system.  I can see the Interop
namespace and root/cimv2, but I cannot figure out how to have it point
to our profiles.  I looked in the openwbem.conf file but could not
figure out where that setting would be.  Where can I set that path?

You will have to import the mof files into the respective namespaces. Xen_RegisteredSVProfile, Xen_RegisteredVSProfile, Xen_ElementConformsToSVProfile and Xen_ElementConformsToVSProfile must reside in multiple namespaces. You can import to arbitrary namespaces using OpenWBEM's mof compiler, e.g.:

owmofc -n Interop Xen_RegisteredSVProfile.mof Xen_RegisteredVSProfile.mof Xen_ElementConformsToSVProfile.mof Xen_ElementConformsToVSProfile.mof

You will need these classes in root/cimv2 as well. Also, since we use smash for host instrumentation , you will need the following in smash namespace:

owmofc -n smash Xen_RegisteredSVProfile.mof Xen_ElementConformsToSVProfile.mof Xen_ComputerSystem.mof Xen_HostedComputerSystem.mof

Sorry for not documenting this. I have built rpms for sles10 that handle importing mof into appropriate namespaces but did not get around to incorporating it into the 'make postinstall' target. This target simply blasts all the mofs into root/cimv2.

Jim


_______________________________________________
Xen-cim mailing list
Xen-cim@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-cim


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.