WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-cim

Re: [Xen-cim] Suggested SettingsData changes

To: Jim Fehlig <jfehlig@xxxxxxxxxx>
Subject: Re: [Xen-cim] Suggested SettingsData changes
From: Gareth S Bestor <bestor@xxxxxxxxxx>
Date: Fri, 12 May 2006 12:38:48 -0700
Cc: xen-cim@xxxxxxxxxxxxxxxxxxx, xen-cim-bounces@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 12 May 2006 12:33:08 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <4463B47D.7040109@xxxxxxxxxx>
List-help: <mailto:xen-cim-request@lists.xensource.com?subject=help>
List-id: xen-cim mailing list <xen-cim.lists.xensource.com>
List-post: <mailto:xen-cim@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-cim>, <mailto:xen-cim-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-cim>, <mailto:xen-cim-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-cim-bounces@xxxxxxxxxxxxxxxxxxx

>Regarding the public availability of DMTF WG mofs, I think we should
>inherit directly from the mofs and for the time just doc it in the
>project - perhaps with a link to the mofs enabling DMTF members to
>access them.  Non-members will not be able to use the providers until
>DMTF has resolved the issue.


As it stands today, the Open Source Xen CIM providers must either have an (out-of-tree) dependency on obtaining the draft DMTF MOFs by some other means [yuck], or else effectively duplicate what is in the draft CIM_* System Virtualization MOFs into our equivalent Xen_* MOFs, which is probably plagiarism and violates the spirit - if not the letter - of the "DMTF confidential" license. So I agree that probably the best bet for now is proceed with making the Xen_* subclasses of the appropriate DMTF CIM_* classes-to-be, provide a link for obtaining the prerequisite DMTF MOFs, and hopefully in a relatively short time we'll get approval or be granted an exception by the DMTF to copy the requisite CIM_* MOFs in-tree.

- Gareth

Dr. Gareth S. Bestor
IBM Linux Technology Center
M/S DES2-01
15300 SW Koll Parkway, Beaverton, OR 97006
503-578-3186, T/L 775-3186, Fax 503-578-3186

Inactive hide details for Jim Fehlig <jfehlig@xxxxxxxxxx>Jim Fehlig <jfehlig@xxxxxxxxxx>


          Jim Fehlig <jfehlig@xxxxxxxxxx>
          Sent by: xen-cim-bounces@xxxxxxxxxxxxxxxxxxx

          05/11/06 03:02 PM


To

xen-cim@xxxxxxxxxxxxxxxxxxx

cc


Subject

[Xen-cim] Suggested SettingsData changes

All,

I have finally gotten around to updating the various SettingsData
classes in the current model with their latest counterparts from the
DMTF WG.  Here is what I am considering thus far.

Remove classes
* Xen_ComputerSystemConfiguration
* Xen_ComputerSystemSetting
* Xen_SettingForComputerSystem
* Xen_ConfigurationForComputerSystem
* Xen_VirtualDeviceSettingData

Modify classes
* Xen_ComputerSystemSettingData
  - Inherit from CIM_VirutalSystemSettingData
  - Move ID, SSID, and Uptime from Xen_ComputerSystemSetting to this class
* Xen_CSSettingDataComponent
  - Inherit from CIM_VirutalSystemSettingDataComponent
* Xen_ProcessorSettingData
  - Inherit from CIM_ResourceAllocationSettingData
* Xen_MemorySettingData
  - Inherit from CIM_ResourceAllocationSettingData
* Xen_DiskSettingData
  - Inherit from CIM_ResourceAllocationSettingData
* Xen_NetworkPortSettingData
  - Inherit from CIM_ResourceAllocationSettingData
* Xen_CSSettingDataComponent
  - Inherit from CIM_VirtualSystemSettingDataComponent

Xen_VirtualDeviceSettingData contains a subset of properties found in
CIM_ResourceAllocationSettingData so removing it should be no problem.

Regarding the public availability of DMTF WG mofs, I think we should
inherit directly from the mofs and for the time just doc it in the
project - perhaps with a link to the mofs enabling DMTF members to
access them.  Non-members will not be able to use the providers until
DMTF has resolved the issue.

I will begin making these changes to the mofs and affected
implementation classes.  Please let me know if there are any objections.

Regards,
Jim

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

GIF image

_______________________________________________
Xen-cim mailing list
Xen-cim@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-cim
<Prev in Thread] Current Thread [Next in Thread>