From 4f84fafbe28ec4b94127c45a0e3e773a2f571eb5 Mon Sep 17 00:00:00 2001 From: Vishakha Agarwal Date: Sat, 20 Oct 2018 22:33:02 +0530 Subject: [PATCH] Updating doc of unified limit 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/ --- doc/source/admin/identity-unified-limits.rst | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/doc/source/admin/identity-unified-limits.rst b/doc/source/admin/identity-unified-limits.rst index c6ff8bca42..3cddcc9821 100644 --- a/doc/source/admin/identity-unified-limits.rst +++ b/doc/source/admin/identity-unified-limits.rst @@ -27,10 +27,16 @@ establish a limit may include: - API service type (e.g. compute, network, object-storage) - a resource type (e.g. ram_mb, vcpus, security-groups) - a default limit -- a project specific limit +- a project specific limit i.e resource limit - user_id (optional) - 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, 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