Tenants are able to set custom compute values during VM creation or modification when using VM Placement Policies

Products

• VMware Cloud Director

Issue/Introduction

• Tenant can bypass T-Shirt Sizing Policies in Cloud Director (VCD).
• Tenant is able to deselect VM Sizing policy on a VM and chose 'none'.
• Provider wants tenants to be restricted to predefined values and to not be able to configure custom CPU or Memory values.
• VM Sizing Policies and VM Placement Policies are both in use by the Tenant.

Environment

VMware Cloud Director 10.6.1.x

Cause

This issue occurs because the VM Placement policy in use was created without VM sizing definitions. VM Placement policies and VM Sizing/T-Shirt Sizing policies are both categorized as Compute Policies. VCD requires that you have one compute policy selected during VM creation or modification in certain Organization VDC types. If the user selects a VM Placement policy which does not have CPU/Memory defined, then they are allowed to specify their own custom compute values.

Resolution

This is expected behavior.

To enforce VM sizing with VM Placement policies in use, then the VM Sizing needs to be defined within the VM Placement itself as outlined in Create a VM Placement Policy within a Provider VDC in VMware Cloud Director

Additional Information

To limit the maximum compute resources that tenants can allocate to individual virtual machines within an organization VDC, system administrators can change the maximum VDC compute policy.