vSAN Management API
| Local Properties | ||
Managed Object Types | Data Object Types | All Properties | All Methods |
Data Object - VsanExtendedConfig(vim.vsan.VsanExtendedConfig)
- Property of
- VimVsanReconfigSpec, VsanConfigInfoEx, VsanHostConfigInfoEx
- Extends
- DynamicData
- See also
- VsanCapacityReservationInfo, VsanProactiveRebalanceInfo
- Since
- 6.7
Data Object Description
vSAN extended configurationsProperties
Name | Type | Description |
---|---|---|
capacityReservationInfo* | VsanCapacityReservationInfo |
Enforce capacity reservation Information.
Refer to VsanCapacityReservationInfo.
Since vSAN 7.0U1 |
disableSiteReadLocality* | xsd:boolean |
By default, site read locality is enabled for vSAN streched
cluster/2 nodes configuration, with this, reads to vSAN object
only occur on the site the VirtualMachine resides on. But with
this setting, we can disable the site read locality, which will
force reads across all mirrors, in low latency vSAN stretched
cluster/2 nodes configuration, this means reads would occur
across both sites in a stretched cluster, which can most
effectively improve the read performance.
|
enableCustomizedSwapObject* | xsd:boolean |
While create swap object for VirtualMachine, policy
'proportionalCapacity' is overwritten by default with value 100,
this means swap object will reserve 100% space of its size on
vSAN datastore. This behavior can be turned off through this
config, allow customer to fully control the policy
'proportionalCapacity' for swap object to save swap spaces.
After set this field to True, swap object policy set on host
through command 'esxcli vsan policy setdefault' will be fully
respected;
|
largeScaleClusterSupport* | xsd:boolean |
By default, vSAN cluster can only grow up to 32 nodes. But by
setting this option, vSAN cluster is allowed to grow up to large
scale, at maximun to 64 nodes. Please be noted, if this option
is changed before vSAN enabled, it can be applied at host side
immediately; but if it is changed on a vSAN cluster, all hosts
are required to reboot to apply this change. After setting this,
please review the vSAN health check result, which can help to
figure out which host requires rebooting.
|
objectRepairTimer* | xsd:long |
This configuration is to determine delay time in minutes for vSAN,
to wait for absent component to come back before starting repair it.
|
proactiveRebalanceInfo* | VsanProactiveRebalanceInfo |
Proactive Rebalance Information.
Refer to VsanProactiveRebalanceInfo.
Since vSAN 6.7U3 |
Properties inherited from DynamicData | ||
None |
Show WSDL type definition
Top of page | Local Properties | ||
Managed Object Types | Data Object Types | All Properties | All Methods |