openstack/keystone
Code Issues Proposed changes

Updating doc of unified limit

Browse Source 
Adding the details of maximum and minimum
values a user can set for default limit,
resource limit and resource name in the
unified limit doc.

Change-Id: I9655fb502b287ed7f0d381498252a24b417e5718
Related-patch: https://review.openstack.org/#/c/610479/
This commit is contained in:
Vishakha Agarwal 2018-10-20 22:33:02 +05:30
parent 6f189e0b02
commit 4f84fafbe2
1 changed files with 7 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
doc/source/admin/identity-unified-limits.rst
View File

@ -27,10 +27,16 @@ establish a limit may include:
- API service type (e.g. compute, network, object-storage) - API service type (e.g. compute, network, object-storage)
- a resource type (e.g. ram_mb, vcpus, security-groups) - a resource type (e.g. ram_mb, vcpus, security-groups)
- a default limit - a default limit
- a project specific limit - a project specific limit i.e resource limit
- user_id (optional) - user_id (optional)
- a region (optional depending on the service) - a region (optional depending on the service)
.. NOTE:: The `default limit` of registered limit and the `resource limit` of
limit now are limited from `-1` to `2147483647` (integer). `-1` means
no limit and `2147483647` is the max value for user to define limits.
The length of unified limit's `resource type` now is limited from `1`
to `255` (string).
Since keystone is the source of truth for nearly everything in the above list, Since keystone is the source of truth for nearly everything in the above list,
limits are a natural fit as a keystone resource. Two different limit resources limits are a natural fit as a keystone resource. Two different limit resources
exist in this design. The first is a registered limit and the second is a exist in this design. The first is a registered limit and the second is a