-
Bug
-
Resolution: Done
-
Major
-
rhos-18.0.z
-
None
-
5
-
False
-
-
False
-
?
-
rhos-storage
-
None
-
-
-
-
Important
The current glance per-tenant quota documentation doesn't have an example to create a project specific quota.
With unified limit, we need to the following steps to configure the project specific quota.
1. Set the deployment wide default quota for glance through openstack registered limit command.
2. Apply the necessary glance config through customServiceConfig for glance in OpenStackControlPlane CR
3. Add system scope permission to glance user
These are already described at https://docs.redhat.com/en/documentation/red_hat_openstack_services_on_openshift/18.0/html/customizing_persistent_storage/assembly_glance-customizing-the-image-service_customizing-cinder#proc_configuring-glance-to-use-project-quotas_glance-quotas
However, there is no description for setting a project specific quota.
From quick research and testing, a user needs to run the following command after registered limit command defines the deployment wide limit.
$ openstack --os-cloud <admin role user> --region-name <region> --project <project name> --service glance --resource-limit <the value of resource limit, e.g.102400> image_size_total
Also, we should describe the operations covered by https://docs.openstack.org/python-openstackclient/2023.1/cli/command-objects/limit.html with specific examples.
- relates to
-
OSPRH-746 Implement Unified Keystone Quotas in Glance
-
- Review
-