Data Object - StorageIOAllocationInfo(vim.StorageResourceManager.IOAllocationInfo)

Property of: VirtualDisk
Extends: DynamicData
See also: SharesInfo
Since: vSphere API Release 4.1

Data Object Description

Deprecated. As of vSphere8.0 U3, and there is no replacement for it.

The IOAllocationInfo specifies the shares, limit and reservation for storage I/O resource.

The storage I/O resource is allocated to virtual machines based on their shares, limit and reservation. The reservation is currently exposed only at the host level for local and shared datastores. We do not support storage I/O resource management on resource pools.

Each virtual machine has one IOAllocationInfo object per virtual disk. For example, we can specify that a virtual machine has 500 shares on the first virtual disk, 1000 shares on the second virtual disk, etc.

Properties

Name	Type	Description
limit*	xsd:long	The utilization of a virtual machine will not exceed this limit, even if there are available resources. This is typically used to ensure a consistent performance of virtual machines independent of available resources. If set to -1, then there is no fixed limit on resource usage (only bounded by available resources and shares). The unit is number of I/O per second. While setting the limit for storage I/O resource, if the property is unset, it is treated as no change and the property is not updated. While reading back the limit information of storage I/O resource, if the property is unset, a default value of -1 will be returned, which indicates that there is no limit on resource usage.
reservation*	xsd:int	Deprecated. As of vSphere8.0 U3, and there is no replacement for it. Reservation control is used to provide guaranteed allocation in terms of IOPS. Large IO sizes are considered as multiple IOs using a chunk size of 32 KB as default. This control is initially supported only at host level for local datastores. It future, it may get supported on shared storage based on integration with Storage IO Control. Also right now we don't do any admission control based on IO reservation values. *Since* vSphere API Release 5.5
shares*	SharesInfo	Deprecated. As of vSphere8.0 U3, and there is no replacement for it. Shares are used in case of resource contention. The value should be within a range of 200 to 4000. While setting shares for storage I/O resource, if the property is unset, it is treated as no change and the property is not updated. While reading back the shares information of storage I/O resource, if the property is unset, a default value of level = normal, shares = 1000 will be returned.
Properties inherited from DynamicData
None

*Need not be set
Show WSDL type definition

         <complexType xmlns="http://www.w3.org/2001/XMLSchema" xmlns:vim25="urn:vim25" name="StorageIOAllocationInfo">
            <complexContent>
               <extension base="vim25:DynamicData">
                  <sequence>
                     <element name="limit" type="xsd:long" minOccurs="0"/>
                     <element name="shares" type="vim25:SharesInfo" minOccurs="0"/>
                     <element name="reservation" type="xsd:int" minOccurs="0"/>
                  </sequence>
               </extension>
            </complexContent>
         </complexType>

vSphere Web Services API

Data Object - StorageIOAllocationInfo(vim.StorageResourceManager.IOAllocationInfo)

Data Object Description