[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-cim] Setting Data Changes
>
1. What is purpose of SystemCreationClassName in
>Xen_VirtualDeviceSettingData? All Xen_*SettingData classes *use* to
>have it since they derived from Xen_VirtualDeviceSettingData.
Implementation pragmatism (programmer laziness? :-) SystemCreationClassName effectively acts as a foreign key, making it easy to implement the necessary association (ie give me all Xen_VirtualDeviceSettingData's where the SystemCreationClassName property matches the Xen_ComputerSystem I am looking at). This basically explicitly exposes the system name component that is/will usually be inside the InstanceID key property. The alternative is that in order to find out what actual (virtual) computer system the setting data info is about you'd have to potentially parse it out of InstanceID. I stole the idea from CIM_SystemSetting, which is the class I was using to store this data before we moved to CIM_SettingData subclasses for everything.
>
3. Should Uptime property be in Xen_ComputerSystemSettingData? It is
>not setting data. I left it for now.
Hmm... You are correct in saying that is is not really 'setting' data. And clearly the base class - CIM_ComputerSystem - doesn't have an existing equivalent property that could be exploited. So I'd say off the top of my head this is perhaps a good candidate for a metric.
- G
Gareth S. Bestor, PhD.
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
Sent by: xen-cim-bounces@xxxxxxxxxxxxxxxxxxx
To: xen-cim@xxxxxxxxxxxxxxxxxxx
cc:
Subject: [Xen-cim] Setting Data Changes
Today I committed changes made to the various settings data classes.
Summary of changes:
* Xen_ComputerSystemSettingData now derives from
CIM_VirtualSystemSettingData
* Xen_CSSettingDataComponent now derives from
CIM_VirtualSystemSettingDataComponent
* Xen_DiskSettingData, Xen_MemorySettingData,
Xen_NetworkPortSettingData, and Xen_ProcessorSettingData now derive from
CIM_ResourceAllocationSettingData
* InstanceID property of all setting data classes now conforms to the
algorithm described in CIM_SettingData. I have used "Xen" as OrgID.
* Added information to README file describing how to build / install
code. Link to SVPC area is included for access to the mofs serving as
base classes for the Xen schema.
* Removed Mutable property from all Xen_*SettingData classes
While making these changes I came across the following issues / questions:
1. What is purpose of SystemCreationClassName in
Xen_VirtualDeviceSettingData? All Xen_*SettingData classes *use* to
have it since they derived from Xen_VirtualDeviceSettingData.
2. Xen_DiskSettingData - what to do with Reservation, Limit,
VirtualQuantity, etc. These properties are currently set to a value of
1. Currently we are not doing anything with Weight property in any of
the setting data classes.
3. Should Uptime property be in Xen_ComputerSystemSettingData? It is
not setting data. I left it for now.
Regards,
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
|
