Class CIM_StorageSetting
extends CIM_SettingData

StorageSetting is roughly equivalent to a Service Level Agreement (SLA) It defines the characteristics, qualities of service and goals when used in a CreateOrModifyElement FromStoragePool or CreateOrModifyStoragePool method in the StorageConfigurationService. It specifies a series of properties with Maximum and Minimum values that define the (inclusive) bounds that the object should maintain. Note that the setting is associated to a StorageVolume, using ElementSetting.

Class Hierarchy

CIM_ManagedElement
   |
   +--CIM_SettingData
   |
   +--CIM_StorageSetting

Direct Known Subclasses

CIM_StorageSettingWithHints

Class Qualifiers

NameData TypeValueScopeFlavors
DescriptionstringStorageSetting is roughly equivalent to a Service Level Agreement (SLA) It defines the characteristics, qualities of service and goals when used in a CreateOrModifyElement FromStoragePool or CreateOrModifyStoragePool method in the StorageConfigurationService. It specifies a series of properties with Maximum and Minimum values that define the (inclusive) bounds that the object should maintain. Note that the setting is associated to a StorageVolume, using ElementSetting.None TRANSLATABLE= true
Versionstring2.7.0TOSUBCLASS= falseTRANSLATABLE= true

Local Class Properties

NameData TypeQualifiers
NameData TypeValueScopeFlavors
Captionstring
DescriptionstringThe Caption property is a short textual description (one- line string) of the object.None TRANSLATABLE= true
MaxLenuint3264None None
DataRedundancyGoaluint16
DescriptionstringDataRedundancyGoal 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.None TRANSLATABLE= true
MinValuesint641None None
ModelCorrespondencestringCIM_StorageSetting.DataRedundancyMax, CIM_StorageSetting.DataRedundancyMinNone None
WritebooleantrueNone None
DataRedundancyMaxuint16
DescriptionstringDataRedundancyMax 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.None TRANSLATABLE= true
MinValuesint641None None
ModelCorrespondencestringCIM_StorageSetting.DataRedundancyMin, CIM_StorageSetting.DataRedundancyGoalNone None
WritebooleantrueNone None
DataRedundancyMinuint16
DescriptionstringDataRedundancyMin 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.None TRANSLATABLE= true
MinValuesint641None None
ModelCorrespondencestringCIM_StorageSetting.DataRedundancyMax, CIM_StorageSetting.DataRedundancyGoalNone None
WritebooleantrueNone None
DeltaReservationGoaluint8
DescriptionstringDeltaReservationGoal 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.None TRANSLATABLE= true
MaxValuesint64100None None
MinValuesint641None None
ModelCorrespondencestringCIM_StorageSetting.DeltaReservationMin, CIM_StorageSetting.DeltaReservationMaxNone None
UnitsstringPercentageNone TRANSLATABLE= true
WritebooleantrueNone None
DeltaReservationMaxuint8
DescriptionstringDeltaReservationMax 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.None TRANSLATABLE= true
MaxValuesint64100None None
MinValuesint641None None
ModelCorrespondencestringCIM_StorageSetting.DeltaReservationMin, CIM_StorageSetting.DeltaReservationGoalNone None
UnitsstringPercentageNone TRANSLATABLE= true
WritebooleantrueNone None
DeltaReservationMinuint8
DescriptionstringDeltaReservationMin 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.None TRANSLATABLE= true
MaxValuesint64100None None
MinValuesint641None None
ModelCorrespondencestringCIM_StorageSetting.DeltaReservationMax, CIM_StorageSetting.DeltaReservationGoalNone None
UnitsstringPercentageNone TRANSLATABLE= true
WritebooleantrueNone None
Descriptionstring
DescriptionstringThe Description property provides a textual description of the object.None TRANSLATABLE= true
ElementNamestring
DescriptionstringThe 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.)None TRANSLATABLE= true
OverridestringElementNameNone OVERRIDABLE= false
RequiredbooleantrueNone OVERRIDABLE= false
InstanceIDstring
DescriptionstringWithin 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'.None TRANSLATABLE= true
KeybooleantrueNone OVERRIDABLE= false
NoSinglePointOfFailureboolean
DescriptionstringIndicates the desired value for No Single Point of Failure. Possible values are false = single point of failure, and true = no single point of failure.None TRANSLATABLE= true
WritebooleantrueNone None
PackageRedundancyGoaluint16
DescriptionstringPackageRedundancyGoal 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.None TRANSLATABLE= true
ModelCorrespondencestringCIM_StorageSetting.PackageRedundancyMax, CIM_StorageSetting.PackageRedundancyMinNone None
WritebooleantrueNone None
PackageRedundancyMaxuint16
DescriptionstringPackageRedundancyMax 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.None TRANSLATABLE= true
ModelCorrespondencestringCIM_StorageSetting.PackageRedundancyMin, CIM_StorageSetting.PackageRedundancyGoalNone None
WritebooleantrueNone None
PackageRedundancyMinuint16
DescriptionstringPackageRedundancyMin 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.None TRANSLATABLE= true
ModelCorrespondencestringCIM_StorageSetting.PackageRedundancyMax, CIM_StorageSetting.PackageRedundancyGoalNone None
WritebooleantrueNone None