[Xen-cim] Detection of host instrumentation

[Jim Fehlig <jfehlig@xxxxxxxxxx>]

After thinking about several approaches for ensuring that host 
instrumentation is available at build time, I've concluded they all suck 
and we should just document this dependency :-).
Detecting existence of dependent providers during configure requires 
asking the cimom (assuming it is running) for a known registered profile 
or class.  This is the only way I see of reliably determining if the 
build host has the required instrumentation - and I'm not comfortable 
doing such hackery in the configure script.
I like the runtime discovery we have previously discussed, but it is 
useless without our own instrumentation to fall back on in the event 
nothing is found - and I don't want to be in the host instrumentation 
business given the existence of OMC, SBLIM, etc.
I have two suggestions for handling the host instrumentation dependency.

1. Just document that the existence of virtualization model depends on 
existence of related modeling.  We could provide instructions in the 
README for obtaining and installing the OMC project and be done with it.
2. Same as above but with added 'feature' of specifying host 
instrumentation via a configure argument.  E.g. one could run 
'./configure --with-omc' or './configure --with-sblim'.  The configure 
script would not detect existence of the instrumentation - just use some 
knowledge about these projects to determine namespace and classnames of 
host instrumentation for use throughout the providers.  If not 
specified, default to OMC.
Option 2 seems reasonable and allows for using SBLIM providers on 
Pegasus until such time OMC providers can run in that environment.  User 
is still responsible for ensuring the host instrumentation is installed 
and functional.
Thoughts?

Jim


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