Fw: [Xen-cim] Suggested SettingsData changes

[Gareth S Bestor <bestor@xxxxxxxxxx>]

Forgot to respond to all...

- G


----- Forwarded by Gareth S Bestor/Beaverton/IBM on 05/12/06 12:54 PM -----

Gareth S Bestor/Beaverton/IBM

05/12/06 12:58 PM

To	"Subrahmanian, Raj" <raj.subrahmanian@xxxxxxxxxx>
cc
Subject	RE: [Xen-cim] Suggested SettingsData changes

I created and used Xen_VirtualDeviceSettingData largely as the stand-in for new CIM_ResourceAllocationSettingData not existing in the CIM schema that I had to build against. Although it really only makes in slight difference in the implementation, unless an abstract Xen_VirtualDeviceSettingData superclass itself will add something meaningful and Xen-specific to the (abstract) CIM_ResourceAllocationSettingData class - which I don't think it will - then my preference would be not to pollute the CIM class model with additional classes for the sake of perhaps minor implementation simplicity. ie ask the Xen_VirtualDeviceSettingData class the question "Justify your existence!" :-)

BTW - you've probably already noticed some of the Xen_* classname suffixes differ from their latest CIM_* counterparts, specifically "VirtualDeviceSettingData" vs "ResouceAllocationSettingData". No reason other than my very early implementation choices while the DMTF modelling was growing up. I'm quite open to renaming the Xen-specific classes to have more appropriate and current names, though I'd rather the class names not become *too* long that they are unmanageable.

- 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

"Subrahmanian, Raj" <raj.subrahmanian@xxxxxxxxxx>

"Subrahmanian, Raj" <raj.subrahmanian@xxxxxxxxxx>
Sent by: xen-cim-bounces@xxxxxxxxxxxxxxxxxxx

05/11/06 03:23 PM

To	"Jim Fehlig" <jfehlig@xxxxxxxxxx>, <xen-cim@xxxxxxxxxxxxxxxxxxx>
cc
Subject	RE: [Xen-cim] Suggested SettingsData changes

I would prefer that we derived Xen_VirtualDeviceSettingData from
CIM_ResourceAllocationSettingData and then have others derive from
Xen_VirtualDeviceSettingData. It seems cleaner.

Raj 

-----Original Message-----
From: xen-cim-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:xen-cim-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Jim Fehlig
Sent: Thursday, May 11, 2006 6:11 PM
To: xen-cim@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-cim] Suggested SettingsData changes

Jim Fehlig wrote:

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


On second thought, perhaps it would be best to derive
Xen_VirtualDeviceSettingData from CIM_ResourceAllocationSettingData and
then have the various resource setting data classes derive from
Xen_VirtualDeviceSettingData.  Thoughts?

Jim


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

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

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