Quotas¶
A quota is an upper limit for how much of a given resource an allocation can use in parallel, for example number of instances or CPU cores. Jetstream2 tries to apportion project quotas based on both allocation size and Jetstream2 resource type.
Quotas are allocation-wide
Resource quotas are shared and contributed to by all users on an allocation. PIs may want to institute informal per‑user quotas or discuss proper usage etiquette with the members of their allocation. Jetstream2 staff will not institute per‑user quotas.
Compute Quotas (CPUs, RAM, Floating IPs, GPUs)¶
Compute quotas are driven by the number of Service Units (SUs) a project allocates to each compute resource, as opposed to other quotas like number of instances and or number of volumes. The three compute resources are CPU, Large Memory (LM), and GPU.
Thresholds¶
| Resource | Scaling threshold (SUs) |
|---|---|
| CPU | 200 000 |
| Large Memory | 400 000 |
| GPU | 600 000 |
If the SUs allocated to a resource are less than the scaling threshold, the project receives the default quotas below. If the allocation exceeds the threshold, the quota is scaled linearly by the scaling factor allocated_SUs / threshold.
Default Quotas (≤ Scaling Threshold)¶
| Resource | vCPU | RAM (GB) | Floating IPs |
|---|---|---|---|
| CPU | 150 | 585 | 10 |
| Large Memory | 128 | 1 000 | 2 |
| GPU | 64 | 250 | 4 |
Multiple Resources¶
When a project allocates SUs to more than one compute resource (for example, both CPU and Large Memory), each resource is evaluated independently against its own scaling threshold.
The quota for a given resource is calculated using the method described above for that resource alone.
After each resource’s quota is determined, the total compute quota is simply the sum of those individual quotas.
Note: The thresholds are not combined or summed; they are applied per‑resource.
GPU Quotas¶
Compute resources for GPU instances still count against the CPU quota limits, but additional limits apply per GPU device type and allocation tier.
| GPU type | Flavors | Explore | Discover | Accelerate | Maximize | NAIRR |
|---|---|---|---|---|---|---|
| Partial (vGPU) | g3.medium, g3.large | - | - | - | - | - |
| Full‑card A100 | g3.xl | 2 | 4 | 4 | 4 | 4 |
| L40S | g4.xl, g4.2xl, g4.4xl | 0 | 0 | 0 | 0 | 1 |
| H100 | g5.xl, g5.2xl, g5.4xl | 0 | 2 | 2 | 2 | 2 |
“0” means the GPU type is not available for that allocation tier. “-” indicates no limit.
Multi‑card instances: Flavors g4.2xl and g4.4xl count as 2 and 4 L40S GPUs respectively; flavors g5.2xl and g5.4xl count as 2 and 4 H100 GPUs respectively. This usage is applied against the limits shown above.
Requesting Quota Changes¶
If the automatically calculated quota does not meet your project’s needs, you may request an increase by contacting Jetstream2 support. Provide a clear justification (e.g., a classroom with 50+ students) and the desired quota values. Support will review the request and adjust the allocation if justified. Due to resource constraints, adjustments to GPU quotas may require additional justification and may take additional time to process.
Storage Quotas¶
While storage is available to facilitate research, Jetstream2 is not primarily a storage service; large‑capacity storage is beyond the scope of Jetstream2.
Default Storage
By default, all allocations receive 1 TB (1000 GB) of Jetstream2 Storage quota. If you will not need more than this, you do not need to request Jetstream2 Storage with your allocation request.
If your project requires it, additional Jetstream2 storage is an ACCESS‑marketplace‑allocated resource and can be requested with an exchange request from the ACCESS Allocations Management Portal by exchanging credits to the Indiana Jetstream2 Storage resource at a rate of 1 ACCESS credit == 1 GB. Please note that all storage requests will require appropriate justification.
Also note that the default 1 TB quota is only a floor, and storage allocations are absolute. In other words, the default 1 TB is replaced by a discrete allocation, not added on top of it. For example, if a project has a Jetstream2 Storage allocation through ACCESS of 3 000 credits/SUs/GB, their total storage quota will be 3 TB (not 3 TB + 1 TB = 4 TB). In this sense, preparing storage exchange requests is simple—just request the amount of total GB needed.
How Do I Increase My Manila or Object Storage Quota?¶
- View your total storage quota in the ACCESS Allocations Management Portal.
- Request a re‑allocation of GB from volume storage to Manila or Object storage via Jetstream2 support (contact page).
- Include in the request: - amount of GB to move, - source storage type (usually volume), - target storage type (Manila or Object).
Your three storage quotas must always sum to the total quota shown in the portal.
Limits on Jetstream2 Storage1¶
- Explore allocations are generally limited to 5 TB max
- Discover allocations are generally limited to 5‑10 TB max
- Accelerate allocations are generally limited to 20 TB max
- Maximize allocations are generally limited to 40 TB max
Other Limits¶
There are additional quotas in place beyond the ones listed above. If you run into your quota limits for any of these, we ask that you first check if any applicable resources can be cleaned up or consolidated. If not, you may need to request an increase from the Jetstream2 team.
Jetstream2 policies may also impact quotas, particularly regarding networking.
How to Check your Quota Limits and Usage¶
There are several ways to check your quota depending on which interface you are using.
Exosphere¶
Quota limits as well as usage are displayed throughout the Exosphere interface. The project dashboard shows basic and usage and quota limits for Instances, Volumes, IP Addresses, etc. Each of these cards can be opened to show more detailed information. For example, clicking on the “Instances” card will show a breakdown of instance, cores, and RAM usage. Exosphere only displays a limited subset of quota information; for the most comprehensive view, use the command line interface (CLI).
Horizon¶
Some Quota limits and usage are displayed on the “Overview” page under the “Compute” section. Horizon only displays a limited subset of quota information; for the most comprehensive view, use the command line interface (CLI).
CLI¶
With project-scoped application credentials, you can check your quota limits and usage using the OpenStack CLI. See Command Line Interface for instructions on setting up the CLI and obtaining application credentials.
Compute, Storage, and Network Quotas¶
openstack quota show --usage
Manila Share Quotas¶
openstack share quota show --detail <project_uuid>
Object Store Quotas¶
openstack object store account show
This will produce output similar to the following, where the Bytes field displays the usage in bytes and the properties field displays the quota limits:
+------------+----------------------------------------------------------------------------------------------------------------------------+
| Field | Value |
+------------+----------------------------------------------------------------------------------------------------------------------------+
| Account | v1 |
| Bytes | 445462004 |
| Containers | 10 |
| Objects | 18 |
| properties | access-control-allow-origin='*', access-control-expose-headers='Access-Control-Allow-Origin', quota-bytes='10995116277760' |
+------------+----------------------------------------------------------------------------------------------------------------------------+
To convert the usage and quota limit output to TB, you can use the following commands:
# Display Usage in TB
openstack object store account show -c Bytes -f value | awk '{print $1 / 1024^4}'
# Display Quota Limit in TB
openstack object store account show -c properties -f json | jq -r '.properties."quota-bytes"' | awk '{print $1 / 1024^4}'
-
All are subject to proper justification in the allocations process. Maximum values may be adjusted with proper justification and if adequate resources are available. This is entirely at the discretion of the Jetstream2 team. ↩