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

[Xen-cim] Fix some mof files


  • To: <xen-cim@xxxxxxxxxxxxxxxxxxx>
  • From: "Subrahmanian, Raj" <raj.subrahmanian@xxxxxxxxxx>
  • Date: Fri, 28 Apr 2006 02:32:58 -0400
  • Delivery-date: Thu, 27 Apr 2006 23:34:16 -0700
  • List-id: xen-cim mailing list <xen-cim.lists.xensource.com>
  • Thread-index: AcZoAKKY0GmKRFeyQ2yfE68501BdUQCh8C+Q
  • Thread-topic: Fix some mof files

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

Attachment: mofpatch.diff
Description: mofpatch.diff

_______________________________________________
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®.