Add Mistral Guide and Assets

docs/content/guides/assets/mistral/mistral.mmd

@@ -0,0 +1,21 @@
+flowchart LR
+classDef Orange fill:#F8773D,stroke:#000000,stroke-width:2px;
+classDef Green fill:#56AE89,stroke:#000000,stroke-width:2px;
+classDef Red fill:#F13C15,stroke:#000000,stroke-width:1px;
+classDef Pink fill:#ffb6c1,stroke:#000000,stroke-width:1px;
+
+TC[\Token Counter/]
+class TC Orange
+
+Scheduler
+class Scheduler Orange
+
+SDK
+class SDK Green
+
+subgraph Aperture_Cloud ["Aperture Cloud"]
+    Scheduler -- "Counting" --> TC
+end
+class Aperture_Cloud Green
+
+SDK -- "Schedule Request" --> Scheduler

docs/content/guides/assets/mistral/mistral.mmd.md5sum

@@ -0,0 +1 @@
+5df63f64375615e3ec9761cb92b987af

docs/content/guides/assets/mistral/policy.yaml

@@ -10,7 +10,6 @@ spec:
     - flow_control:
         concurrency_scheduler:
           concurrency_limiter:
-            limit_by_label_key: limit_by_label_key
             max_inflight_duration: 60s
           in_ports:
             max_concurrency:

docs/content/guides/assets/mistral/validate.sh

@@ -0,0 +1,22 @@
+#!/usr/bin/env bash
+
+set -e
+
+git_root=$(git rev-parse --show-toplevel)
+
+# shellcheck disable=SC1091
+source "$git_root"/docs/tools/aperturectl/validate_common.sh
+
+generate_from_values \
+	values.yaml \
+	tmp
+
+# copy the generated policy and graph to this (assets) directory so that they can be used in the docs
+cp tmp/policies/mistral-concurrency-scheduling-cr.yaml policy.yaml
+cp tmp/graphs/mistral-concurrency-scheduling-cr.mmd graph.mmd
+
+# git add the generated policy and graph
+"$git_root"/scripts/git_add_safely.sh policy.yaml graph.mmd
+
+# remove the tmp directory
+rm -rf tmp

docs/content/guides/assets/mistral/values.yaml

@@ -0,0 +1,21 @@
+# yaml-language-server: $schema=../../../../../blueprints/concurrency-scheduling/base/gen/definitions.json
+blueprint: concurrency-scheduling/base
+uri: ../../../../../blueprints
+policy:
+  policy_name: "mistral-concurrency-scheduling"
+  components: []
+  concurrency_scheduler:
+    alerter:
+      alert_name: "Too many inflight requests"
+    concurrency_limiter:
+      max_inflight_duration: "60s"
+    max_concurrency: 2
+    scheduler:
+      priority_label_key: "priority"
+      tokens_label_key: "tokens"
+      workload_label_key: "workload"
+    selectors:
+      - control_point: "mistral-prompt"
+  resources:
+    flow_control:
+      classifiers: []

docs/content/guides/concurrency-quota-management.md

@@ -32,7 +32,7 @@
 
 Concurrency quota management, also called concurrency scheduling, is a
 sophisticated technique that allows effective management of concurrent requests.
 With this technique services can limit the number of concurrent API calls to
 alleviate the load on the system.
 
 When service limits are reached, Aperture Cloud can queue incoming requests and
@@ -55,7 +55,7 @@
 of which is defined by its priority and weight. This classification is crucial
 for the request scheduling process.
 
 The scheduler priorities request admission based the priority and weight
 assigned to the corresponding workload. This mechanism ensures that
 high-priority requests are handled appropriately even under high load.
 
@@ -70,7 +70,7 @@
 
 ## Concurrency Scheduling with Aperture SDK
 
 The first step to using the Aperture SDK is to import and set up Aperture
 Client:
 
 ```mdx-code-block
@@ -146,23 +146,23 @@
 ```
 
 Navigate to the `Policies` tab on the sidebar menu, and select `Create Policy`
 in the upper right corner. Next, choose the Request Prioritization blueprint,
 and from the drop-down options select Concurrency based. Now, complete the form
 with these specific values:
 
 1. `Policy Name`: Unique for each policy, this field can be used to define
    policies tailored for different use cases. Set the policy name to
    `concurrency-scheduling-test`.
 2. `Limit by label key`: Determines the specific label key used for concurrency
    limits. We'll use `user_id` as an example.
 3. `Max inflight duration`: Configures the time duration after which flow is
    assumed to have ended in case the end call gets missed. We'll set it to `60s`
    as an example.
 4. `Max concurrency`: Configures the maximum number of concurrent requests that
    a service can take. We'll set it to `20` as an example.
 5. `Priority label key`: This field specifies the label that is used to
    determine the priority. We will leave the label as it is.
 6. `Tokens label key`: This field specifies the label that is used to determine
    tokens. We will leave the label as it is.
 7. `Workload label key`: This field specifies the label that is used to
    determine the workload. We will leave the label as it is.
@@ -249,7 +249,7 @@
 menu. Copy and enter both your Organization address and API Key to establish a
 connection between the SDK and Aperture Cloud.
 
-## Monitoring concurrency Scheduling Policy
+## Monitoring Concurrency Scheduling Policy
 
 After running the example for a few minutes, you can review the telemetry data
 in the Aperture Cloud UI. Navigate to the Aperture Cloud UI, and click the