Compartment quotas in Oracle Cloud Infrastructure are applied to control the usage and growth of resources within a compartment. Each compartment has its own set of quotas that define the maximum amount of resources that can be created or used.
Quotas are applied to various resources such as instances, block volumes, and object storage. The quotas are enforced when a user tries to create or modify a resource that would exceed the quota limit.
Compartment quotas are applied at the time of resource creation, and they are not retroactively applied to existing resources. This means that if a user has already created a resource that exceeds the quota limit, the quota will not be enforced until the user tries to create or modify another resource.
The quota limits are set by the administrator and can be adjusted as needed to manage resource usage and growth within a compartment.
Basic Concepts
Compartment quotas in Oracle Cloud Infrastructure (OCI) are limits set on the resources that can be consumed within a specific compartment. This helps in managing resources effectively and ensuring that no single compartment can exhaust the resources available to the entire tenancy.
Compartment quotas give tenant and compartment administrators better control over resource usage in OCI. Administrators can efficiently allocate resources to compartments using the Console. This empowerment allows administrators to readily distribute resources to compartments.
Compartment quotas are established by crafting policy statements written in a declarative language, similar to IAM policies. There are three types of quota policy statements available:
- set: Sets the maximum number of a cloud resource that can be used for a compartment.
- unset: Resets quotas back to the default service limits.
- zero: Removes access to a cloud resource for a compartment.
Quotas can be applied in different scopes, including per-compartment basis, per-region basis, globally, and per-tenancy basis. In OCI, compartment quotas are specifically applied on a per-compartment basis, allowing for tailored resource management.
Manage Resource Availability
Compartment quotas in Oracle Cloud Infrastructure (OCI) allow you to manage resource availability on a per-compartment basis. This means each compartment can have its own set of resource limits, allowing for tailored resource management.
You can restrict the availability of dedicated infrastructure resources in your tenancy, such as OCPUs, ECPUs, and total data storage for Autonomous Data Warehouse and Autonomous Transaction Processing databases.
To manage resource availability, you can use the compartment quotas feature to set, unset, or zero out quotas for specific cloud resources. For example, you can set the maximum number of cloud resources that can be used for a compartment, or reset quotas back to the default service limits.
Here are some examples of quota statements:
- set database quota atp-dedicated-ocpu-count to 3 in compartment MyCompartment
- unset database quota atp-dedicated-ocpu-count in tenancy
- zero email-delivery quotas in compartment MyCompartment
- zero notifications quotas in compartment MyCompartment
You can find more examples and quota policy syntax in the Sample Quotas section. Additionally, you can use the OCI Console's Limits, Quotas and Usage page to automatically generate quota statements.
Verification and Troubleshooting
You can verify the quota settings for a compartment in Oracle Cloud Infrastructure by checking the Quota tab in the compartment's details page.
Compartment quotas are applied based on the type of resource, such as Compute, Storage, or Network.
To troubleshoot quota issues, you can check the quota usage for a specific resource type in the Quota tab.
If a quota is exceeded, you won't be able to create a new resource, but you can still view and manage existing resources.
To resolve quota issues, you can increase the quota for a compartment by clicking the "Increase Quota" button in the Quota tab.
Quota changes take effect immediately, but you can also schedule quota changes for a later time if needed.
Guides and Resources
Compartment quotas are applied in Oracle Cloud Infrastructure to limit the resources available to a compartment.
The default quota for a root compartment is 10 times the default quota for a non-root compartment. This is because the root compartment is the top-level compartment in the tenancy.
You can view and manage quotas for a compartment using the Oracle Cloud Infrastructure Console or the CLI. The CLI command to view quotas is "oci compartment get-quota".
To increase the quota for a compartment, you need to submit a request to Oracle support. The request must include a justification for the increase and the desired quota amount.
The quota for a compartment can be increased up to the default quota for the tenancy. This is because the default quota for the tenancy is the maximum quota that can be applied to any compartment.
Sources
- https://docs.oracle.com/en-us/iaas/autonomous-database/doc/manage-resource-availability-compartment-quotas.html
- https://surajramesh.com/mastering-resource-management-a-guide-to-compartment-quotas-in-oracle-cloud-infrastructure
- https://r-cubedsolutions.com/2023/01/11/oci-compartments-guide-part-1-of-4/
- https://medium.com/@jhasamiree1/oracle-cloud-infrastructure-quota-policies-ecf25e175dbb
- https://studyx.ai/homework/108175081-how-are-compartment-quotas-applied-in-oracle-cloud-infrastructure-on-a-per-compartment
Featured Images: pexels.com