Cloud.vSphere.Disk
Request schema for provisioning of vSphere Storage
{
"SCSIController": "string",
"account": "string",
"capacityGb": 0,
"constraints": [
{
"tag": "string"
}
],
"count": 0,
"dataStore": "string",
"encrypted": false,
"maxDiskCapacityInGB": 0,
"name": "string",
"persistent": false,
"providerId": "string",
"provisioningType": "string",
"region": "string",
"storagePolicy": "string",
"tags": [
{
"key": "string",
"value": "string"
}
],
"unitNumber": 0
}The SCSI controller to be assigned
Cloud Account indicates the name of the endpoint used to provision this machine.
Disk size in gigabytes.
To create the correct storage at provisioning time, blueprint constraints are matched against infrastructure capability tags. Constraints must include the key name. Options include value, negative [!], and hard or soft requirement.
The number of resource instances to be created.
The vSphere datastore in which to create the disk.
Whether or not the disk is encrypted.
Maximum disk size allowed for create or resize disk operation
Disk name.
Indicates that the disk will survive machine or deployment deletion
A unique identifier of the resource in the context of the provider.
The vSphere provisioning type to use at provisioning time: thick, thin, or eagerZeroedThick.
Datacenter name where the disk landed.
The vSphere storage policy to follow at provisioning time. A storage policy can reference storage capabilities advertised by a storage entity.
Tags
Unit Number to be assigned