[Xen-cim] Various implementation questions

[Jim Fehlig <jfehlig@xxxxxxxxxx>]

While thinking about integrating SMASH with our Xen providers, several 
questions came to mind.
Using OMC_<Some Class> directly in mofs (primarily in association 
classes) and in the code creates a dependency on OMC project.  Do we 
really want such a dependency?  We could do some build-time trick to 
generate mofs and headers with selected host instrumentation, and fall 
back to CIM_<Some Class> if nothing is specified and no reasonable 
default (e.g. OMC) is found.  The only problem I have with this 
dependency is it is "out of tree".  Users of xen-cim will have to go yet 
another place (already have to get libvirt) for dependencies.  Using OMC 
exclusively is certainly the easiest, so if we don't feel this is an 
issue I will just go that route.
Looking into resource pools and how SMASH providers integrate there, I 
debated how host resources added to a pool will be persisted.  E.g. a 
host has 8 processors and management app creates a ProcessorResourcePool 
and then adds all host processors.  A ConcreteComponent association 
between the pool and each device must be persisted.  One simple solution 
is to create an instance of the association and stash it in local CIMOM 
instance repository.  Other suggestions?
BTW, there is a lot off association traversal in resource pool 
implementations.  E.g. consider one approach to creating an instance 
with just capacity and reservation properties populated:  Traverse all 
ConcreateComponent associations to get the "real" logical device, 
summing to generate capacity.  Then traverse all 
ElementAllocatedFromPool associations to get "virtual" logical device, 
summing to get reservation.  For the latter, you could optionally 
traverse ResourceAllocationFromPool to get RASD for each virtual device, 
summing these to generate reservation.
Probably had some other questions but can't think of them now :-).

Jim



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