Total Pageviews

Resource Quota Policy in vRealize Automation 8.5


VMware has finally introduced the long-awaited feature Resource Quota Policy in  vRealize Automation 8.5.In this  blog, I am going to describe, how to setup resource quota Limit (Memory, CPU, VM count and storage) for project and project Users.

vRA 8.4 does support three types of policies, which are mentioned below and Resource Quota Policy has been introduce in vRA 8.5  

  • Approval policy
  • Day 2 Actions policy
  • Lease policy 
Latest release of vRealize Automation 8.5 ,VMware is introducing a new type of policy called “Resource Quota Policy” which provides  vRA SME to limit the consumption of their resources (VM, CPU, memory, and storage). This policy can be configured to set a limit on resource usage. When a user requests a new deployment, the resource quota policy kicks in and will not allow the deployment to go through if the limits of the resources set in the policy are reached. The request fails and an appropriate error message is displayed in the deployment history. 

Let start to Configure Resource Quota Policy. 

To set a new resource quota policy,  

  1. Go to Service Broker  
  2. Click on Content and Policies  
  3. Go to Policies 
  4. Click on Definitions 
  5. Click on the “NEW POLICY” button 
Graphical user interface, text, application, chat or text message

Description automatically generated


The next screen shows all Policy Types available in vRA 8.5 


Click on the new tile for the Resource Quota Policy. 

Graphical user interface, application

Description automatically generated

The first step is to provide a name followed by an optional description of this policy. 


Graphical user interface, text, application, email

Description automatically generated 

 The next two fields (“Scope” and Resource quota” )  are mandatory to define the quota.



  1. 1-  When you select “Organization / Multiple Projects”, you can choose to specify the names of projects by clicking the “+” button and either providing specific names or a regular expression which would apply to all projects that meet this criterion. If you do not include project names, by default, the policy is applied at the org level.

  2.  

  1. 2- You can also choose to apply this policy to a specific Project. For that, select the radio button for “Project” and select the project in the field that appears. As you can see above print screen.

  2.  

Finally need to add resource quota limits by clicking the “ADD” button. In the Add Resource Quota” pop up, you select the type of limit, the name of the resource and set its limits. 


Graphical user interface, application

Description automatically generated


Now you have the option to choose the “Type” of limits at organization, organization user, project or project user level. Here’s what each type means. 


  1. Organization Limits: The resource quota is applied at the org level as an aggregate of resources consumed by all users. 
  2. Organization User Limits: The resource quota is applied at the org level per user in that org. A user could belong to multiple projects in which case the aggregate of resources in all such projects is considered before enforcing a limit if the projects belong to that org.
  3. Project Limits: The resource quota is applied at the project level as an aggregate of resources consumed by all users. 
  4. Project User Limits: The resource quota is applied at the project level per user in that project. 

When you select the scope as Project, the “Scope level” is restricted to Project Limits and Project User Limits. 


The “Resource” field gives you an option to apply the limit to one of CPU, VM Count, Memory or Storage. 


Graphical user interface, application

Description automatically generated




Depending on the resource selection, the format of the value that you provide in the “Limit” field will be enforced. For “CPU” and “VM Count”, it is an absolute number. For “Memory” and “Storage”, it is the size in GB. 


Graphical user interface

Description automatically generated


After providing all the necessary details, click Create to save the new policy. Now you can verify that the new policy has been successfully created. 

I hope you enjoy reading this blog as much as I enjoyed writing it. Feel free to share this on social media if it is worth sharing.



No comments:

Post a Comment

Deploy Windows VMs for vRealize Automation Installation using vRealize Suite Lifecycle Manager 2.0

Deploy Windows VMs for vRealize Automation Installation using vRealize Suite Lifecycle Manager 2.0 In this post I am going to describe ...