×
 
 
  •  
$helper.renderConfluenceMacro('{bmc-global-announcement:$space.key}')

Unsupported content

 

This version of the product has reached end of support. The documentation is available for your convenience. However, you must be logged in to access it. You will not be able to leave comments.
BMC Cloud Lifecycle Management 4.5 ... Administering the product Tenants

Setting and managing quota

In BMC Cloud Lifecycle Management, one can determine the ability to allocate and monitor resources to the tenants or users. By default, unlimited quota is allocated to the tenants and maximum quota for the users.

A cloud administrator can determine how many resources can be allocated to any tenant depending upon the tenant's requirement. Users are assigned quota from the quota of the tenant to which they belong.

You can specify the following resources:

  • Server: Specifies the number of servers to be allocated to a tenant or a user.
  • CPU Count: Specifies the number of CPUs to be allocated to a tenant or a user.
  • Memory (GB): Specifies the memory to be allocated to a tenant or a user, in GB. 
  • Local Storage (GB): Specifies the local hard disk to be allocated to a tenant or a user, in GB.

When a user provisions a service offering instance, the quota is available either from the user's allocated quota or from the available tenant quota (in case user's quota is maximum). If the requested quota exceeds the available quota, the service offering instance or the TRO action fails. When a service offering instance is transferred from one owner to another within the same tenant or across different tenants, the user and the tenant quota is updated. When you synchronize the service offering instances, the quota details are updated for the user and the tenant. When you delete a user, the quota is released and the tenant and the user quota is updated.

The tenant quota is calculated based on the allocated user quota plus the actual provisioned quota for the users who have been allocated maximum quota.

If a tenant surpasses its quota, a service request cannot be provisioned until the tenant is allocated more quota or some of the existing quota is released. When you click OK, depending on which resource is less, the following error message is displayed.

The following topics describe the process to set the tenant and the user quota.

Note

When you delete a system disk from a provisioned VM, the Provision Deployment Model is not updated; however, the quota details are updated for the SOI.

Related topic

Quota management overview

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Last modified by Lisa Greene on Jul 27, 2016
edit_review quota

Comments

Log in or register to comment.

Creating and managing users in BMC Cloud Lifecycle Management
Setting tenant quota
© Copyright 2024 BMC Software, Inc.
Legal notices

Powered by Atlassian Confluence and Scroll Viewport

© Copyright 2005-2024 BMC Software, Inc. Use of this site signifies your acceptance of BMC’s Terms of Use . BMC, the BMC logo, and other BMC marks are assets of BMC Software, Inc. These trademarks are registered and may be registered in the U.S. and in other countries.