Google Cloud uses quotas to help ensure fairness and reduce spikes in resource use and availability. A quota restricts how much of a Google Cloud resource your Google Cloud project can use. Quotas apply to a range of resource types, including hardware, software, and network components. For example, quotas can restrict the number of API calls to a service, the number of load balancers used concurrently by your project, or the number of projects that you can create. Quotas protect the community of Google Cloud users by preventing the overloading of services. Quotas also help you to manage your own Google Cloud resources.
The Cloud Quotas system does the following:
- Monitors your consumption of Google Cloud products and services
- Restricts your consumption of those resources
- Provides a way to request changes to the quota value and automate quota adjustments
In most cases, when you attempt to consume more of a resource than its quota allows, the system blocks access to the resource, and the task that you're trying to perform fails.
Quotas generally apply at the Google Cloud project level. Your use of a resource in one project doesn't affect your available quota in another project. Within a Google Cloud project, quotas are shared across all applications and IP addresses.
For more information, see the Cloud Quotas overview.
Quotas for required services
To successfully create clusters in Cluster Director, you must first obtain sufficient quota for both of the following resource categories:
Quota for sending requests to the Cluster Director API.
Quota for the required compute, storage, and networking services that your clusters use.
Otherwise, you encounter errors. To view quota values for one or more resources, see View and manage quotas.
The following sections describe the necessary service quotas that you must have to create, view, update, or delete clusters in Cluster Director.
Quotas for the Cluster Director API
The Cluster Director API uses quotas to control how often you can send requests to the API, as well as the number of active clusters that you can have in your project.
The available quotas for the Cluster Director API are as follows:
| Quota name | Description |
|---|---|
| Cluster Director clusters per region | Restricts the total number of active clusters that can be in your project and per region. |
| Create requests per minute per region | Restricts how often you can send requests to the
v1beta clusters.create method per minute and per
region. |
| Delete requests per minute per region | Restricts how often you can send requests to the
v1beta clusters.delete method per minute and per
region. |
| Get requests per minute per region | Restricts how often you can send requests to the
v1beta clusters.get method per minute and per region.
|
| List requests per minute per region | Restricts how often you can send requests to the
v1beta clusters.list method per minute and per region.
|
| Update requests per minute per region | Restricts how often you can send requests to the
v1beta clusters.update method per minute and per
region. |
Quotas for compute, storage, and networking services
Cluster Director relies on the following underlying services to deploy cluster components. You must have sufficient quota for all of the following:
Compute Engine: you must have sufficient Compute Engine quota for creating virtual machine (VM) instances and any resources that are attached to your VMs, such as GPUs or Local SSD disks. This quota includes regional quota, which controls the number of VMs that you can create in a region.
For more information, see the quotas and system limits for Compute Engine.
Filestore: you must have sufficient Filestore quota to create Filestore instances in your cluster. Filestore instances are mandatory for creating Slurm clusters in Cluster Director.
For more information, see the quotas and system limits for Filestore.
Networking: you must have sufficient networking quota to create Virtual Private Cloud (VPC) networks, subnets, external IP addresses, and configure firewall rules that are necessary for cluster communication and access.
For more information, see the quotas and system limits for VPC.
Quotas for optional storage services
If you plan to use optional storage services in your cluster besides a mandatory Filestore instance, then you must verify that you have sufficient quota for one or both of the following services:
Cloud Storage: you must have sufficient Cloud Storage quota to use Cloud Storage buckets as a storage service.
For more information, see the quotas and system limits for Cloud Storage.
Google Cloud Managed Lustre: you must have sufficient Managed Lustre quota to use Managed Lustre instances as a storage service.
For more information, see the quotas and system limits for Managed Lustre.