openstack/oslo.limit
Code Issues Proposed changes

Fix doc grammar/spelling nits

Browse Source 
As a result, this commit message is guaranteed to have a grammar or
spelling error.[1] ;-)

Change-Id: Ie941d36a7e3d7918a18dc71735307451835d3038
1: https://en.wikipedia.org/wiki/Muphry%27s_law
This commit is contained in:
Ben Nemec 2018-09-24 20:46:13 +00:00
parent e575be7d5e
commit c91ca64438
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
doc/source/user/usage.rst
View File

@ -12,7 +12,7 @@ Conceptual Overview
This library is meant to aid service developers performing usage checks for
resources managed by their service. It does this by clearly defining what is
being claim, where resources are being claimed, and encapsulating enforcement
being claimed, where resources are being claimed, and encapsulating enforcement
logic behind easy-to-use utilities. The following subsections introduce common
terms and concepts useful for communicating within the context of usage
enforcement for distributed systems.
@ -35,7 +35,7 @@ A limit is the total number of resources someone or something *should* have.
With respect to OpenStack, the service which owns a particular resource may
also own that resource's limit. Conversely, limit information may be
centralized in a shared service. The later is the pattern implied by the usage
centralized in a shared service. The latter is the pattern implied by the usage
of this library. The justification for decoupling resource limits from
individual services is to make it easier to provide a consistent experience for
users or operators setting and enforcing limits, regardless of the resource.
@ -43,20 +43,20 @@ users or operators setting and enforcing limits, regardless of the resource.
Claim
-----
A claim represent the quantity of resources being asked for by someone. Claims
A claim represents the quantity of resources being asked for by someone. Claims
are constrained by the relationship between resource usage and limits.
Successful claims are aggregated into usage.
Within the OpenStack ecosystem, claims can be made against specific targets
depending on the resource. For instance, a user may request two additional
servers for her project. This resulting claim might be two instances, the total
number of cores between both instance, the total memory consumed by both
number of cores between both instances, the total memory consumed by both
instances, or all three. The claim is also targeted to a specific project,
which affects how this library asks for usage information.
Enforcement
-----------
Enforcement is the process of collection usage data, limit information, and
Enforcement is the process of collecting usage data, limit information, and
claims in order to make a decision about whether a user should be able to
obtain more resources.