OLS-1622: Document token quota feature

configure/ols-configuring-openshift-lightspeed.adoc

@@ -23,3 +23,5 @@ include::modules/ols-about-lightspeed-and-role-based-access-control.adoc[levelof
 include::modules/ols-granting-access-to-individual-users.adoc[leveloffset=+2]
 include::modules/ols-granting-access-to-user-group.adoc[leveloffset=+2]
 include::modules/ols-filtering-and-redacting-information.adoc[leveloffset=+1]
+include::modules/ols-tokens-and-token-quota-limits.adoc[leveloffset=+1]
+include::modules/ols-activating-token-quota-limits.adoc[leveloffset=+2]

modules/ols-activating-token-quota-limits.adoc

@@ -0,0 +1,69 @@
+// Module included in the following assemblies:
+// * TBD
+
+:_mod-docs-content-type: PROCEDURE
+[id="ols-activating-token-quota-limits_{context}"]
+= Activating token quota limits
+
+Activate token quota limits for the {ols-long} Service by defining key-value pairs in the `ConfigMap` resource. The {ols-long} pod mounts the `ConfigMap` resource as a volume, enabling access to the file stored within it. The `OLSConfig` Custom Resource (CR) references the `ConfigMap` resource to obtain the quota limit information.
+
+.Prerequisites
+
+* You have installed the the {ols-long} Operator.
+
+* You have configured a large language model provider (LLM).
+
+* A PostgresSQL database is configured and the {ols-long} Service can access the database.
+
+.Procedure
+
+. Open the {ols-long} `ConfigMap` file by running the following command:
++
+[source,terminal]
+----
+$ oc edit configmap <configmap_filename>
+----
+
+. Modify the `data` property of the `ConfigMap` file to include token quota limit information.
++
+.Example {ols-long} `ConfigMap` file
+[source,yaml]
+----
+apiVersion: v1
+kind: ConfigMap
+metadata:
+  name: quota-limit
+  namespace: openshift-lightspeed
+data:
+  quota_handlers.conf: 
+    storage:
+      host: <IP_address> <1>
+      port: "5432"
+      dbname: <database_name>
+      user: <user_name>
+      password_path: <file_containing_database_password>
+      ssl_mode: disable
+    limiters:
+      - name: user_monthly_limits 
+        type: user_limiter
+        initial_quota: 100000 <2>
+        quota_increase: 10
+        period: 30 days
+      - name: cluster_monthly_limits 
+        type: cluster_limiter
+        quota_increase: 1000000 <3>
+        period: 30 days
+    scheduler:
+      period: 300 <4>
+----
+<1> Specifies the IP address for the PostgresSQL database. The database must use port `5432`.
+<2> Specifies a token quota limit of 100,000 for each user over a period of 30 days.
+<3> Increases the token quota limit for the cluster by 100,000 over a period of 30 days.
+<4> Defines the number of seconds that the scheduler waits and then checks if the period interval is over. When the period interval is over, the scheduler stores the timestamp and resets or increases the quota limit.
+
+. Apply the `ConfigMap` file so that the token limit quota takes effect by running the following command:
++
+[source,terminal]
+----
+$ oc apply -f <configmap_name>
+----

modules/ols-tokens-and-token-quota-limits.adoc

@@ -0,0 +1,12 @@
+// Module included in the following assemblies:
+// * TBD
+
+:_mod-docs-content-type: CONCEPT
+[id="ols-tokens-and-token-quota-limits_{context}"]
+= Tokens and token quota limits
+
+Tokens are small chunks of text, which can be as small as one character or as large as one word. Tokens are the units of measurement used to quantify the amount of text that the {ols-long} Service sends to, or receives from, a large language model (LLM). Every interaction with the Service and the LLM is counted in tokens.
+
+Token quota limits define the number of tokens that can be used in a certain timeframe. Implementing token quota limits helps control costs, encourage more efficient use of queries, and regulate system demands. In a multi-user configuration, token quota limits help provide equal access to all users ensuring everyone has an opportunity to submit queries. 
+
+You can define token quota limits for {ocp-short-name} clusters or {ocp-short-name} user accounts.