public class FaultToleranceVMConfigSpec extends DynamicData
Java class for FaultToleranceVMConfigSpec complex type.
The following schema fragment specifies the expected content contained within this class.
<complexType name="FaultToleranceVMConfigSpec">
<complexContent>
<extension base="{urn:vim25}DynamicData">
<sequence>
<element name="vmConfig" type="{urn:vim25}ManagedObjectReference" minOccurs="0"/>
<element name="disks" type="{urn:vim25}FaultToleranceDiskSpec" maxOccurs="unbounded" minOccurs="0"/>
</sequence>
</extension>
</complexContent>
</complexType>
| Modifier and Type | Field and Description |
|---|---|
protected List<FaultToleranceDiskSpec> |
disks |
protected ManagedObjectReference |
vmConfig |
| Constructor and Description |
|---|
FaultToleranceVMConfigSpec() |
| Modifier and Type | Method and Description |
|---|---|
List<FaultToleranceDiskSpec> |
getDisks()
Gets the value of the disks property.
|
ManagedObjectReference |
getVmConfig()
Gets the value of the vmConfig property.
|
void |
setVmConfig(ManagedObjectReference value)
Sets the value of the vmConfig property.
|
protected ManagedObjectReference vmConfig
protected List<FaultToleranceDiskSpec> disks
public ManagedObjectReference getVmConfig()
ManagedObjectReferencepublic void setVmConfig(ManagedObjectReference value)
value - allowed object is
ManagedObjectReferencepublic List<FaultToleranceDiskSpec> getDisks()
This accessor method returns a reference to the live list,
not a snapshot. Therefore any modification you make to the
returned list will be present inside the JAXB object.
This is why there is not a set method for the disks property.
For example, to add a new item, do as follows:
getDisks().add(newItem);
Objects of the following type(s) are allowed in the list
FaultToleranceDiskSpec
Copyright © 2018. All rights reserved.