VMware Aria Automation Tools

 View Only

 How to change bootdisk provisioningType in Cloud Template?

Jump to  Best Answer
Jinhoe's profile image
Jinhoe posted Sep 20, 2024 11:51 PM

Hi, how can I change bootdisk provisioningType in Cloud Template? I want user to have the option to choose between thin or thick provisioning.

I know this can be done in Cloud.vSphere.Disk, but provisioningType schema wasn't available in Cloud.vSphere.Machine.

Please advice, thank you.

Cloud_vSphere_Machine_1:
  type: Cloud.vSphere.Machine
  allocatePerInstance: true
  properties:
    image: Ubuntu
    flavor: Small
    storage:
      bootDiskCapacityInGB: 20
Jinhoe's profile image
Jinhoe  Best Answer

I used Storage Profiles and Capability Tags to get the job done.

tarek_nader's profile image
tarek_nader

Use below under 'properties':

properties:
    provisioningType: thin

Or
properties:
    provisioningType: thick
In most cases, requests would create thin provisioning storage by default. However, if the cloud template has the provisioningType property set to eager-zero, the cloud template overrides the default of thin.

Note: When you want exact control, it's better to add capability and constraint tags labeled for the desired provisioning type.

Cloud_vSphere_Machine_1:
  type: Cloud.vSphere.Machine
  allocatePerInstance: true
  properties:
    image: Ubuntu
    flavor: Small
    storage:
      bootDiskCapacityInGB: 20
Sravan_k's profile image
Sravan_k
  • If you want to allow the user to select between different bootdisk provisioning types, you can use properties or input parameters in the Cloud Template to make it configurable at deployment time.
  • If you are using a custom property or configuration for disks, make sure that it is correctly referenced in the Cloud Template YAML structure.
Sravan_k's profile image
Sravan_k

That's a great approach! Using Storage Profiles and Capability Tags in vRealize Automation (vRA) to control the boot disk provisioning provides a more flexible and dynamic method to manage storage resources. This method allows you to leverage existing storage policies in your vSphere environment while keeping the Cloud Template more abstracted and easier to manage.