Device\CIM_StorageSettingWithHints.mof.mof (HTML version)

Return to index
CIM_StorageSettingWithHints Superclass: CIM_StorageSetting
This subclass of StorageSetting allows a client to specify 'hint's for optimization of the volume performance. The effect of these hints is implementation dependent.
Qualifiers:Version ( "2.7.1" )
Parameters (local in grey)
MinValue ( 0 )
Write
MaxValue ( 10 )
uint16 StorageCostHint ;
This hint is an indication of the importance the client places on the cost of storage. Values are 0=Don't Care to 10=Very Important. A StorageVolume provider might choose to place data on low cost or high cost drives based on this parameter.
MinValue ( 0 )
Write
MaxValue ( 10 )
uint16 StorageEfficiencyHint ;
This hint is an indication of the importance placed on storage space efficiency by the client. Values are 0=Don't Care to 10=Very Important. A StorageVolume provider might choose different RAID levels based on this hint.
MinValue ( 0 )
Write
MaxValue ( 10 )
uint16 DataAvailabilityHint ;
This hint is an indication from a client of the importance placed on data availability. Values are 0=Don't Care to 10=Very Important.
MinValue ( 0 )
Write
MaxValue ( 10 )
uint16 AccessLatencyHint ;
This hint is an indication from a client how important access latency is. Values are 0=Don't Care to 10=Very Important.
MinValue ( 0 )
Write
MaxValue ( 10 )
uint16 AccessRandomnessHint ;
This hint is an indication from a client of the randomness of accesses. Values are 0=Entirely Sequential to 10=Entirely Random.
MinValue ( 0 )
Write
MaxValue ( 10 )
uint16 AccessDirectionHint ;
This hint is an indication from a client of the direction of accesses. Values are 0=Entirely Read to 10=Entirely Write.
Write
Units ( "Bytes" )
uint16 AccessSizeHint [ ] ;
This hint is an indication from a client of the optimal access sizes (in bytes). Since this property is an array, several sizes can be specified.
MinValue ( 0 )
Write
MaxValue ( 10 )
uint16 AccessBandwidthWeight ;
This hint is an indication from a client of bandwidth prioritization. Values are 0=Don't Care to 10=Very Important.
Write
ModelCorrespondence { "CIM_StorageSetting.PackageRedundancyMax" , "CIM_StorageSetting.PackageRedundancyGoal" }
uint16 PackageRedundancyMin ;
PackageRedundancyMin describes the minimum number of redundant packages to be used. For example, in the storage domain, package redundancy describes how many disk spindles can fail without data loss including, at most, one spare. An example would be RAID5 with a spare disk which would have a PackageRedundancy of 2. Possible values are 0 to n. The desired redundancy is specified using PackageRedundancyGoal, while the maximum is defined by PackageRedundancyMax.
MinValue ( 1 )
Write
ModelCorrespondence { "CIM_StorageSetting.DataRedundancyMax" , "CIM_StorageSetting.DataRedundancyGoal" }
uint16 DataRedundancyMin ;
DataRedundancyMin describes the minimum number of complete copies of data to be maintained. Examples would be RAID 5 where 1 copy is maintained and RAID 1 where 2 or more copies are maintained. Possible values are 1 to n. The desired redundancy is specified using DataRedundancyGoal, while the maximum is defined by DataRedundancyMax.
Write
ModelCorrespondence { "CIM_StorageSetting.PackageRedundancyMin" , "CIM_StorageSetting.PackageRedundancyGoal" }
uint16 PackageRedundancyMax ;
PackageRedundancyMax describes the maximum number of redundant packages to be used. For example, in the storage domain, package redundancy describes how many disk spindles can fail without data loss including, at most, one spare. An example would be RAID5 with a spare disk which would have a PackageRedundancy of 2. Possible values are 0 to n. The desired redundancy is specified using PackageRedundancyGoal, while the minimum is defined by PackageRedundancyMin.
MinValue ( 1 )
Write
ModelCorrespondence { "CIM_StorageSetting.DeltaReservationMin" , "CIM_StorageSetting.DeltaReservationMax" }
MaxValue ( 100 )
Units ( "Percentage" )
uint8 DeltaReservationGoal ;
DeltaReservationGoal is a number between 1 (1%) and a 100 (100%) which specifies the desired amount of space that should be reserved in a replica for caching changes. For a complete copy this would be 100%. The bounds (max and min) for the reservation are defined using the properties, DeltaReservationMax and DeltaReservationMin.
MinValue ( 1 )
Write
ModelCorrespondence { "CIM_StorageSetting.DataRedundancyMin" , "CIM_StorageSetting.DataRedundancyGoal" }
uint16 DataRedundancyMax ;
DataRedundancyMax describes the maximum number of complete copies of data to be maintained. Examples would be RAID 5 where 1 copy is maintained and RAID 1 where 2 or more copies are maintained. Possible values are 1 to n. The desired redundancy is specified using DataRedundancyGoal, while the minimum is defined by DataRedundancyMin.
MinValue ( 1 )
Write
ModelCorrespondence { "CIM_StorageSetting.DataRedundancyMax" , "CIM_StorageSetting.DataRedundancyMin" }
uint16 DataRedundancyGoal ;
DataRedundancyGoal describes the desired number of complete copies of data to be maintained. Examples would be RAID 5 where 1 copy is maintained and RAID 1 where 2 or more copies are maintained. Possible values are 1 to n. The bounds (max and min) for redundancy are defined using the properties, DataRedundancyMax and DataRedundancyMin.
Write
ModelCorrespondence { "CIM_StorageSetting.PackageRedundancyMax" , "CIM_StorageSetting.PackageRedundancyMin" }
uint16 PackageRedundancyGoal ;
PackageRedundancyGoal describes the desired number of redundant packages to be used. For example, in the storage domain, package redundancy describes how many disk spindles can fail without data loss including, at most, one spare. An example would be RAID5 with a spare disk which would have a PackageRedundancy of 2. Possible values are 0 to n. The bounds (max and min) for redundancy are defined using the properties, PackageRedundancyMax and PackageRedundancyMin.
MinValue ( 1 )
Write
ModelCorrespondence { "CIM_StorageSetting.DeltaReservationMax" , "CIM_StorageSetting.DeltaReservationGoal" }
MaxValue ( 100 )
Units ( "Percentage" )
uint8 DeltaReservationMin ;
DeltaReservationMin is a number between 1 (1%) and a 100 (100%) which specifies the minimum amount of space that should be reserved in a replica for caching changes. For a complete copy this would be 100%. The desired reservation is specified using DeltaReservationGoal, while the maximum is defined by DeltaReservationMax.
MinValue ( 1 )
Write
ModelCorrespondence { "CIM_StorageSetting.DeltaReservationMin" , "CIM_StorageSetting.DeltaReservationGoal" }
MaxValue ( 100 )
Units ( "Percentage" )
uint8 DeltaReservationMax ;
DeltaReservationMax is a number between 1 (1%) and a 100 (100%) which specifies the maximum amount of space that should be reserved in a replica for caching changes. For a complete copy this would be 100%. The desired reservation is specified using DeltaReservationGoal, while the minimum is defined by DeltaReservationMin.
Write
boolean NoSinglePointOfFailure ;
Indicates the desired value for No Single Point of Failure. Possible values are false = single point of failure, and true = no single point of failure.
Required
Override ( "ElementName" )
string ElementName ;
The user friendly name for this instance of SettingData. In addition, the user friendly name can be used as a index property for a search of query. (Note: Name does not have to be unique within a namespace.)
Key
string InstanceID ;
Within the scope of the instantiating Namespace, InstanceID opaquely and uniquely identifies an instance of this class. In order to ensure uniqueness within the NameSpace, the value of InstanceID SHOULD be constructed using the following 'preferred' algorithm:
<OrgID>:<LocalID>
Where <OrgID> and <LocalID> are separated by a colon ':', and where <OrgID> MUST include a copyrighted, trademarked or otherwise unique name that is owned by the business entity creating/defining the InstanceID, or is a registered ID that is assigned to the business entity by a recognized global authority (This is similar to the <Schema Name>_<Class Name> structure of Schema class names.) In addition, to ensure uniqueness <OrgID> MUST NOT contain a colon (':'). When using this algorithm, the first colon to appear in InstanceID MUST appear between <OrgID> and <LocalID>.
<LocalID> is chosen by the business entity and SHOULD not be re-used to identify different underlying (real-world) elements. If the above 'preferred' algorithm is not used, the defining entity MUST assure that the resultant InstanceID is not re-used across any InstanceIDs produced by this or other providers for this instance's NameSpace.
For DMTF defined instances, the 'preferred' algorithm MUST be used with the <OrgID> set to 'CIM'.
MaxLen ( 64 )
string Caption ;
The Caption property is a short textual description (one- line string) of the object.
string Description ;
The Description property provides a textual description of the object.