LMI_VGStorageCapabilities

Class reference

Subclass of CIM_StorageCapabilities

This class represents capability of LMI_StorageConfigurationService to create Volume Groups. It describes, which properties and which values can be used in LMI_VGStorageSetting.

There are no additional properties for now.

Key properties

Local properties

uint16 PackageRedundancyMax

PackageRedundancyMax describes the maximum number of redundant packages that can 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 default redundancy is specified using PackageRedundancyDefault, while the maximum is defined by PackageRedundancyMax.

uint16 DataRedundancyMin

DataRedundancyMin describes the minimum number of complete copies of data that can 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 default redundancy is specified using DataRedundancyDefault, while the maximum is defined by DataRedundancyMax.

boolean NoSinglePointOfFailure

Indicates whether or not the associated element supports no single point of failure. Values are: FALSE = does not support no single point of failure, and TRUE = supports no single point of failure.

uint16 PackageRedundancyDefault

PackageRedundancyDefault describes the default number of redundant packages that will 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 for redundancy are specified using the properties, PackageRedundancyMax and PackageRedundancyMin.

string ElementName

The user friendly name for this instance of Capabilities. 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.)

uint64 ExtentSizeDefault

Default size of Volume Group physical extents.

uint16 DataRedundancyDefault

DataRedundancyDefault describes the default number of complete copies of data that can 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 for the redundancy (max and min) are defined by DataRedundancyMax and DataRedundancyMin.

boolean NoSinglePointOfFailureDefault

Indicates the default value for the NoSinglePointOfFailure property.

uint16 ExtentStripeLengthDefault

Extent Stripe Length describes the number of underlying StorageExtents across which data is striped in the common striping-based storage organizations. This is also known as the number of ‘members’ or ‘columns’.

A NULL value for ExtentStripeLengthDefault indicates that the system does not support configuration of storage by specifying Stripe Length.

If Extent Stripe Length is supported, and this Capabilities instance is associated with a pool that was created with a range of QOS then ExtentStripeLengthDefault represents the default value. Other available values(such as min, max, and discrete values) can be determined by using the ‘GetSupportedStripeLengths’ and ‘GetSupportedStripeLengthRange’ methods.

If Extent Stripe Length is supported and the pool was created with a single specific QOS, representing a Raid group, set, or rank, then this property represents the current/fixed value for the pool, and Extent Stripe Length is not supported in subsequent creation of elements from this pool. Consequently, the ‘GetSupportedStripeLength’ methods cannot be used, and in a StorageSetting instance used as a goal when creating or modifying a child element of the pool, ExtentStripeLengthGoal, ExtentStripeLengthMin, and ExtentStripeLengthMax MUST be set to NULL.

uint16 DataRedundancyMax

DataRedundancyMax describes the maximum number of complete copies of data that can 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 default redundancy is specified using DataRedundancyDefault, while the minimum is defined by DataRedundancyMin.

uint16 PackageRedundancyMin

PackageRedundancyMin describes the minimum number of redundant packages that can 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 default redundancy is specified using PackageRedundancyDefault, while the minimum is defined by PackageRedundancyMin.

Local methods

uint32 CreateVGStorageSetting (InExtents[] CIM_StorageExtent, LMI_StorageSetting Setting)

This method creates new instance of LMI_VGStorageSetting. Applications then do not need to calculate DataRedundancy, PackageRedundancy and ExtentStripeLength.

ValueMap Values
0 Success
1 Not Supported
4 Failed

Parameters

IN InExtents[] CIM_StorageExtent

List of devices, from which the new Volume Group will be created. The created LMI_VGStorageSetting will take redundancy and striping of these devices into account.

That means, to create volume group on top of two devices, the application passes InExtents=(FirstExtent, SecondExtent). Resulting LMI_VGStorageSetting will have DataRedundancy, PackageRedundancy and ExtentStripeLength as minimum of both input extents, indicating that the created Volume Group does not add any additional redundancy or stripping.

For example if the application wants to create volume group on top of two RAID1 devices, it passes InExtents = (FirstRAID1Extent, SecondRAID1Extent). Resulting LMI_MDRAIDStorageSetting will have DataRedundancy, PackageRedundancy and ExtentStripeLength as the minimum of the first and the second RAID1 extents.

OUT LMI_StorageSetting Setting
Created LMI_StorageSetting.

Table Of Contents

Previous topic

LMI_VGElementSettingData

Next topic

LMI_VGStoragePool

This Page