provisioningType property is no longer respected in 8.18.0 and above with improvements to deterministic placement and storage profiles / policies

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

• You are using VMware Aria Automation 8.x and recently upgraded to 8.18.x
• You previously used provisioningType explicitly in your blueprints to define the disk to be set as Thick/Thin/EagerZero.
  • When disks are provisioned, they do not respect the provisioningType set in the blueprint.
• You are not currently using Storage Profiles, and no Storage Profiles have been created.

Environment

VMware Aria Automation 8.x

Cause

Beginning with versions 8.18.x and above, feature improvements were released for deterministic datastore and storage profile selection.

Resolution

Prerequisites

• Version your blueprints before making any changes.

Procedure

1. Create new storage profiles for each disk provisioningType
2. Add a capability tag to these profiles, then assign them to be used in the blueprint.
3. Override the provisioningType set in the storage profile with the provisioningType you prefer.

Example:

Cloud_vSphere_Disk_1:
  type: Cloud.vSphere.Disk.1
  properties:
    capacityGB: 1
    provisioningType: thick
  constraints:
    - tag: 'profile:ThickStorage'

 

Cloud_vSphere.Machine_1:
  type: Cloud.vSphere.Machine
  properties:
    name: '${input.name}'
            - name: 'vSphereBootDiskStorageProfile'
      sizeGB: '${input.bootDiskSize}'
      provisioningType: thick
      constraints:
        - tag: 'profile:ThickStorage'

 

 

 

 

 

Additional Information

https://techdocs.broadcom.com/us/en/vmware-cis/aria/aria-automation/8-18/vmware-aria-automation-release-notes.html