Quota management overview
In BMC Cloud Lifecycle Management, you can determine the ability to allocate and monitor resources to a tenant or to a cloud user. By default, unlimited quota is allocated to the tenants and maximum quota is allocated to the cloud users. You can use quotas with the following environments:
- VMware vSphere
- Amazon Web Services (AWS)
- Amazon Elastic Compute Cloud (Amazon EC2)
- Microsoft Azure (Azure)
- Microsoft Hyper-V
A cloud administrator can determine the number of resources to be allocated to any tenant depending upon the tenant's requirement. Cloud users are assigned quota from the tenant quota to which they belong.
You can specify the following resources:
- Server: Number of servers to be allocated to a tenant or a cloud user
- CPU Count: Number of CPUs to be allocated to a tenant or a cloud user
- Memory (GB): Memory to be allocated to a tenant or a cloud user, in GB
- Local Storage (GB): Local hard disk to be allocated to a tenant or a cloud user, in GB
The following figure illustrates the relationship between the tenant quota and the user quota when the tenant quota is limited:
The following figure illustrates the relationship between the tenant quota and the user quota when the tenant quota is unlimited:
Consider the following scenario – you have both VMware and AWS as services and you define your quota. Here quotas are defined per tenant and then are subdivided into users. In this scenario, if the same tenant is mapped to both VMware and AWS hosting environments, quota consumption is decided based on the VMs in both of these environments. When the service offering instance is provisioned successfully, the user quota and the tenant quota gets updated.
If needed, you can define separate quotas for different environments, say that you have both AWS and Azure. But you must map the hosting environments to different tenants. If the same tenant is mapped to both these environments, then the quota is always an aggregate of both platforms.
In Amazon EC2 provisioning, the blueprint data is not considered and quota is updated as per the actual provisioned servers on Amazon EC2. When a cloud user provisions a service offering instance, the cloud user avails quota from the allocated user quota. If a user is allocated maximum quota, the user utilizes the quota from the available tenant quota. If the available quota is less than the requested quota, the service offering request fails. 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. The quota requirement in a service offering instance is based on the service blueprint.
When a cloud administrator transfers a service offering instance (SOI) to a cloud user within the same tenant, the transfer is successful only if the cloud user who receives the SOI has adequate quota. When the SOI is transferred successfully, the quota from the new owner's allocated quota is deducted for the SOI. Quota from the original owner is released. While the SOI is being transferred, the quota for the recipient cloud user is displayed. In addition, quota calculation does not depend on the power status of the VM – whether the SOI is powered on or powered off. As long as the VM exists, the quota is considered consumed by that VM.
When a user is allocated a virtual machine, the quota is deducted from the user's Available to allocate quota and the user and the tenant quota is updated.
If the configuration is changed in VMware vSphere, and you synchronize the service offering instance, the Synchronize activity is completed successfully, and the new VM configuration is updated for the service offering instance in BMC Cloud Lifecycle Management and the quota is updated for the user and the tenant. The Syncronize activity is completed even if the quota exceeds the available quota and is shown in the Actual usage and Utilization column.
When you decommission a service offering instance, the quota is released and the tenant and the user quota is updated.
When you run the transaction requestable offering (TRO) for quota resources, you can change the configuration for the service offering instance or the VM and the user and the tenant quota gets updated based on the values that you specify. The TRO is successful if the configuration values are equal to or less than the available quota. After applying the TRO, if the new configuration exceeds the available user/tenant quota, the TRO action fails.
A cloud end user can now view quota allocated to the user from the BMC Cloud Lifecycle Management – My Cloud Services Console. This enables a user to provision a service offering request based on the available quota. A cloud end user can only view the quota details and cannot change it.
If any cloud tenant administrator is assigned with multiple tenants, the quota for the cloud tenant administrator is unlimited for the tenant in which the cloud tenant administrator is created. In such a case, no quota is assigned in other tenants.