8.2. Project quota types and limits for the Image service
You can configure and customize image quotas for projects in your OpenStackControlPlane custom resource (CR) file.
You configure the following quotas by using the quotas field in the glance template. When you configure these quotas, the glance-operator registers the quotas in the Identity service (keystone).
You can set a registered limit or a project-specific resource limit to an integer value from -1 to 2,147,483,647. A value of -1 indicates that no limit is set, and 2,147,483,647 is the maximum limit you can set.
| Quota | Description | Default |
|---|---|---|
|
| The maximum amount of storage (in MiB) that the project has for active images. Images with multiple locations contribute to this count, for example, if you have a single 1GiB image stored in four locations, the usage is 4 GiB. Set the value to at least the size of the largest image you expect a user to use. | 1,000 MiB |
|
| The total amount of staging space that might be used. Set the value to at least the size of the largest image you expect a user to use, and allow or limit a user to import one or more images at the same time. | 1,000 MiB |
|
| The number of parallel upload operations that can be in progress at any single point in time. | 0 |
|
| The maximum number of image objects that the user might have, regardless of the size of individual or collective image objects. | 0 |
image_size_cap-
The
image_size_caplimit is the global limit on the size of a single image, and this limit is not registered in the Identity service. You configureimage_size_capin thecustomServiceConfigsection of theglancetemplate in yourOpenStackControlPlaneCR file. The default value is 1 TB.