You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
docs(model-serving): add captured screenshots for Deployment Presets (PR C)
Captures 4 of 6 planned screenshots × 4 languages (16 PNGs):
- deployment_preset_list.png
- admin_deployment_preset_list.png
- deployment_preset_create_modal.png
- vfolder_deploy_preset_detail.png
Skipped (TODO markers retained):
- deployment_preset_edit_modal.png (optional per plan; same layout as create)
- deployment_preset_tag_filter.png (test backend has no preset with tags applied)
Captured at 2× zoom via Portless dev against isla-sorna test backend, per-locale via window.switchLanguage().
Copy file name to clipboardExpand all lines: packages/backend.ai-webui-docs/src/en/model_serving/deployment_presets.md
+6-10Lines changed: 6 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,8 +4,7 @@
4
4
5
5
A **Deployment Preset** is a reusable, administrator-curated bundle of deployment settings — image, runtime, resource slots, cluster mode, environment variables, startup command, replica count, visibility, and other defaults — that end users can apply when they create a model deployment from a storage folder. Presets let administrators publish a small set of vetted, known-good deployment shapes (for example, *vLLM-GPU-Large* or *SGLang-CPU-Small*) so that end users can deploy a model without having to choose every advanced field from scratch.
6
6
7
-

8
-
<!-- TODO: Capture screenshot of the deployment preset list (user view) -->
7
+

9
8
10
9
:::info
11
10
Deployment Presets are part of the Model Serving feature set introduced in version 26.4. Cross-references to preset-aware revision creation are documented in the [Model Serving](#model-serving) page.
@@ -35,8 +34,7 @@ Each preset stores the following deployment defaults:
35
34
36
35
Administrators manage deployment presets from the admin Model Serving area on the **Deployment Presets** tab.
37
36
38
-

39
-
<!-- TODO: Capture screenshot of the admin deployment preset list -->
37
+

40
38
41
39
The list view shows each preset with its name, runtime, image, rank, and key resource fields. From this list, administrators can:
42
40
@@ -65,8 +63,7 @@ The list view shows each preset with its name, runtime, image, rank, and key res
65
63
***Open to Public**: Whether the endpoint of deployments created from this preset is reachable without an access token by default.
66
64
-**Advanced** (optional): Model definition JSON for custom runtimes.
67
65
68
-

69
-
<!-- TODO: Capture screenshot of the deployment preset create modal -->
66
+

70
67
71
68
3. Click **Create Preset** to save. A success notification confirms the preset has been created.
72
69
@@ -80,7 +77,7 @@ If a required field is missing or invalid, the **Create Preset** button stays di
80
77
2. The *Edit Preset* dialog opens with the preset's current values pre-filled. The available sections are identical to the *Create Preset* dialog.
81
78
3. Adjust the fields as needed, then click **Edit Preset** to save your changes.
82
79
83
-

80
+

84
81
<!-- TODO: Capture screenshot of the deployment preset edit modal (optional, same layout as create) -->
85
82
86
83
Editing a preset only changes the defaults for **future** deployments. Existing deployments that were already created from this preset are not modified.
@@ -103,8 +100,7 @@ End users apply a deployment preset through the **VFolder Deploy** modal, which
103
100
2. The VFolder Deploy modal opens, listing the deployment presets available for your project.
104
101
3. Click a preset row to open its **Deployment Preset Detail** view. The detail view shows every field that the preset will apply when used — image, runtime, resources, cluster mode, replica count, visibility, and so on.
105
102
106
-

107
-
<!-- TODO: Capture screenshot of the deployment preset detail in the VFolderDeployModal -->
103
+

108
104
109
105
4. From the detail view, choose how to proceed:
110
106
@@ -136,7 +132,7 @@ If the auto-selected resource preset is the right one for your workload, leave i
136
132
137
133
Both the user-facing preset list and the admin preset list support **clickable tag chips** that filter the list to presets sharing the clicked tag.
138
134
139
-

135
+

140
136
<!-- TODO: Capture screenshot of the deployment preset list filtered by a tag chip -->
141
137
142
138
1. Locate a preset row that has the tag you want to filter by.
0 commit comments