anchor.diff:      secrets: "10" <4>
       services: "10" <5>
   ----
  -<1> The total number of config maps that can exist in the project
  -<2> The total number of persistent volume claims that can exist in the project
  -<3> The total number of replication controllers that can exist in the project
  -<4> The total number of secrets that can exist in the project
  -<5> The total number of services that can exist in the project
  -====
  -
  -compute-resources.yaml
  +<1> The total number of `*ConfigMap*` objects that can exist in the project.
  +<2> The total number of persistent volume claims (PVCs) that can exist in the
  +project.
  +<3> The total number of replication controllers that can exist in the project.
  +<4> The total number of secrets that can exist in the project.
  +<5> The total number of services that can exist in the project.
  +====
  +
  +.*_compute-resources.yaml_*
   ====
   ----
   apiVersion: v1
  
positive.code:     limits.cpu: "2" <4>
      limits.memory: 2Gi <5>
  ----
  <1> The total number of pods in a non-terminal state that can exist in the project
  <2> Across all pods in a non-terminal state, the sum of cpu requests cannot exceed 1 core
  <3> Across all pods in a non-terminal state, the sum of memory requests cannot exceed 1Gi
  <4> Across all pods in a non-terminal state, the sum of cpu limits cannot exceed 2 cores
  <5> Across all pods in a non-terminal state, the sum of memory limits cannot exceed 2Gi
  ====
  
  besteffort.yaml
  ====
  ----
  apiVersion: v1
  
negative.code:   scopes:
    - BestEffort <2>
  ----
  <1> The total number of pods in a non-terminal state with *BestEffort* quality
  of service that can exist in the project.
  <2> Restricts the quota to only matching pods that have *BestEffort* quality of
  service for either memory or CPU.
  ====
  
  [[create-a-quota]]
  == Creating a Quota
  
  To create a quota, first define the quota to your specifications in a file, for
  example as seen in
  link:../admin_guide/quota.html#sample-resource-quota-definitions[Sample Resource
  Quota Definitions]. Then, create using that file to apply it to a project:
  
  ----
  $ oc create -f <resource_quota_definition> [-n <project_name>]
  ----
  
  For example:
  
  ----
  $ oc create -f resource-quota.json -n demoproject
  ----
  
  [[viewing-a-quota]]
  == Viewing a Quota
  
  To view usage statistics related to any hard limits defined in a quota, first
  get the list of quotas defined in the project. For example, for a project called
  *demoproject*:
  
  ====
  ----
  $ oc get quota -n demoproject
  NAME                AGE
  besteffort          11m
  compute-resources   2m
  object-counts       29m
  ----
  ====
  
  Then, describe the resource quota you are interested in, for example a
  *object-counts* quota:
  
  ====
  ----
  $ oc describe quota object-counts -n demoproject
  Name:			object-counts
  Namespace:		demoproject
  Resource		Used	Hard
  --------		----	----
  configmaps		3	10
  persistentvolumeclaims	0	4
  replicationcontrollers	3	20
  secrets			9	10
  services		2	10
  ----
  ====
  
  [[configuring-quota-sync-period]]
  == Configuring Quota Synchronization Period
  
  When a set of resources are deleted, the synchronization time frame of resources
  is determined by the `*resource-quota-sync-period*` setting in the
  *_/etc/origin/master/master-config.yaml_* file.
  
  Before quota usage is restored, a user may encounter problems when attempting to
  reuse the resources. You can change the `*resource-quota-sync-period*` setting
  to have the set of resources regenerate at the desired amount of time (in
  seconds) and for the resources to be available again:
  
  ====
  ----
  