This
(minor) patch fixes the following
-
XenComputerSystem derives from CIM_VirtualComputerSystem
- Some
occurences of Linux_XXXX occurrences changed to CIM_XXXX
occurrences.
After
seeing some of the code and browsing through the documentation, I have a few
questions. I have not yet had the opportunity to thoroughly study the System
Virtualization Profile Document, so please bear with me if I am asking something
that's already answered elsewhere.
- Is
our goal to have our provider ultimately follow the model described in the DMTF
System Virtualization Profile Document?
- I am
having trouble imagining how the whole thing is going to be orchestrated, for
instance, I can see how the Xen_ComputerSystem provider can control
the lifecycle of its VM, but how does the VirtualSystemManagementService talk to
it or tell it what to do?
Thanks
Raj
mofpatch.diff
Description: mofpatch.diff
_______________________________________________
Xen-cim mailing list
Xen-cim@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-cim
|