Skip to content

docs(model-serving): add Deployment Preset management documentation#7444

Open
yomybaby wants to merge 2 commits into
05-18-docs_model-serving_capture_endpoint_detail_ready-alert_and_replica-filter_screenshotsfrom
05-15-docs_model-serving_add_deployment_preset_management_documentation
Open

docs(model-serving): add Deployment Preset management documentation#7444
yomybaby wants to merge 2 commits into
05-18-docs_model-serving_capture_endpoint_detail_ready-alert_and_replica-filter_screenshotsfrom
05-15-docs_model-serving_add_deployment_preset_management_documentation

Conversation

@yomybaby
Copy link
Copy Markdown
Member

resolves #NNN (FR-MMM)

Checklist: (if applicable)

  • Documentation
  • Minium required manager version
  • Specific setting for review (eg., KB link, endpoint or how to setup)
  • Minimum requirements to check during review
  • Test case(s) to demonstrate the difference of before/after

Copy link
Copy Markdown
Member Author

yomybaby commented May 16, 2026

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more


How to use the Graphite Merge Queue

Add either label to this PR to merge it via the merge queue:

  • flow:merge-queue - adds this PR to the back of the merge queue
  • flow:hotfix - for urgent changes, fast-track this PR to the front of the merge queue

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has required the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds multilingual Backend.AI WebUI user manual documentation for Deployment Preset management in Model Serving, and exposes the new page in the docs navigation.

Changes:

  • Added Deployment Presets documentation pages for English, Korean, Japanese, and Thai.
  • Added navigation entries for the new page in all four supported locales.
  • Documented admin preset management, VFolder deployment usage, launcher defaults, and tag filtering.

Reviewed changes

Copilot reviewed 5 out of 21 changed files in this pull request and generated 4 comments.

Show a summary per file
File Description
packages/backend.ai-webui-docs/src/en/model_serving/deployment_presets.md Adds English Deployment Presets documentation.
packages/backend.ai-webui-docs/src/ko/model_serving/deployment_presets.md Adds Korean translation of the new page.
packages/backend.ai-webui-docs/src/ja/model_serving/deployment_presets.md Adds Japanese translation of the new page.
packages/backend.ai-webui-docs/src/th/model_serving/deployment_presets.md Adds Thai translation of the new page.
packages/backend.ai-webui-docs/src/book.config.yaml Adds Deployment Presets to navigation for all locales.
Comments suppressed due to low confidence (24)

packages/backend.ai-webui-docs/src/en/model_serving/deployment_presets.md:108

  • This flow does not match the implemented VFolder deployment UI. VFolderDeployModal shows a preset selector plus an info-icon detail modal, and the detail modal is read-only; there are no clickable preset rows or Auto-deploy/Manual deploy choices in that detail view. Auto-deploy happens automatically only when there is exactly one preset and one resource group. As written, users are instructed to use controls that do not exist.
2. The VFolder Deploy modal opens, listing the deployment presets available for your project.
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.

   ![](images/vfolder_deploy_preset_detail.png)

4. From the detail view, choose how to proceed:

   - **Auto-deploy**: Create the deployment immediately using the preset's values as-is. This is the fastest path; the deployment is created in one click with no further input required.
   - **Manual deploy** (*Create New Deployment with Preset*): Open the deployment launcher with all fields pre-populated from the preset, so you can review and adjust before confirming.

packages/backend.ai-webui-docs/src/ko/model_serving/deployment_presets.md:108

  • This flow does not match the implemented VFolder deployment UI. VFolderDeployModal shows a preset selector plus an info-icon detail modal, and the detail modal is read-only; there are no clickable preset rows or Auto-deploy/Manual deploy choices in that detail view. Auto-deploy happens automatically only when there is exactly one preset and one resource group. As written, users are instructed to use controls that do not exist.
2. VFolder Deploy 모달이 열리고 현재 프로젝트에서 사용 가능한 배포 프리셋이 나열됩니다.
3. 프리셋 행을 클릭하면 **배포 프리셋 상세** 화면이 열립니다. 이 화면에는 프리셋이 적용될 모든 필드(이미지, 런타임, 자원, 클러스터 모드, 레플리카 수, 공개 여부 등)가 표시됩니다.

   ![](images/vfolder_deploy_preset_detail.png)

4. 상세 화면에서 다음 두 가지 방법 중 하나를 선택합니다.

   - **Auto-deploy(자동 배포)**: 프리셋의 값을 그대로 사용하여 즉시 배포를 생성합니다. 추가 입력 없이 한 번의 클릭으로 배포가 시작되는 가장 빠른 경로입니다.
   - **Manual deploy(수동 배포)** (*프리셋으로 새 배포 생성*): 모든 필드가 프리셋의 값으로 미리 채워진 배포 런처를 열어, 확정 전에 검토 및 조정할 수 있습니다.

packages/backend.ai-webui-docs/src/ja/model_serving/deployment_presets.md:108

  • This flow does not match the implemented VFolder deployment UI. VFolderDeployModal shows a preset selector plus an info-icon detail modal, and the detail modal is read-only; there are no clickable preset rows or Auto-deploy/Manual deploy choices in that detail view. Auto-deploy happens automatically only when there is exactly one preset and one resource group. As written, users are instructed to use controls that do not exist.
2. VFolder Deploy モーダルが開き、現在のプロジェクトで利用可能なデプロイメントプリセットが一覧表示されます。
3. プリセット行をクリックすると **デプロイメントプリセット詳細** 画面が開きます。詳細画面には、プリセットが適用するすべての項目(イメージ、ランタイム、リソース、クラスターモード、レプリカ数、公開可否など)が表示されます。

   ![](images/vfolder_deploy_preset_detail.png)

4. 詳細画面で次のいずれかを選択します。

   - **Auto-deploy(自動デプロイ)**:プリセットの値をそのまま使用してすぐにデプロイを作成します。追加入力なしの 1 クリックで完了する最速の経路です。
   - **Manual deploy(手動デプロイ)** (*プリセットで新規デプロイメント作成*):すべてのフィールドがプリセットの値で事前入力されたデプロイランチャーを開き、確定前に確認・調整できます。

packages/backend.ai-webui-docs/src/th/model_serving/deployment_presets.md:108

  • This flow does not match the implemented VFolder deployment UI. VFolderDeployModal shows a preset selector plus an info-icon detail modal, and the detail modal is read-only; there are no clickable preset rows or Auto-deploy/Manual deploy choices in that detail view. Auto-deploy happens automatically only when there is exactly one preset and one resource group. As written, users are instructed to use controls that do not exist.
2. โมดอล VFolder Deploy จะเปิดขึ้นและแสดงรายการพรีเซ็ตการดีพลอยที่ใช้งานได้สำหรับโปรเจกต์ของคุณ
3. คลิกแถวพรีเซ็ตเพื่อเปิดหน้า **รายละเอียดพรีเซ็ตการปรับใช้** หน้านี้จะแสดงทุกฟิลด์ที่พรีเซ็ตจะนำไปใช้ ทั้ง image, runtime, ทรัพยากร, cluster mode, จำนวน replica, การเผยแพร่ และอื่น ๆ

   ![](images/vfolder_deploy_preset_detail.png)

4. จากหน้ารายละเอียด เลือกวิธีดำเนินการต่อ:

   - **Auto-deploy**: สร้าง deployment ทันทีโดยใช้ค่าของพรีเซ็ตตามที่กำหนดไว้ เป็นเส้นทางที่เร็วที่สุด เนื่องจาก deployment ถูกสร้างขึ้นด้วยการคลิกเพียงครั้งเดียวโดยไม่ต้องป้อนข้อมูลเพิ่มเติม
   - **Manual deploy** (*สร้าง Deployment ใหม่ด้วย Preset*): เปิด deployment launcher โดยเติมทุกฟิลด์จากพรีเซ็ตล่วงหน้า ทำให้คุณสามารถตรวจสอบและปรับแต่งก่อนยืนยันได้

packages/backend.ai-webui-docs/src/en/model_serving/deployment_presets.md:123

  • This section describes a manual-deploy launcher being pre-filled from the selected preset, but the VFolder preset flow implemented in VFolderDeployModal does not open a deployment launcher. It either auto-deploys directly, or shows a small modal where the user selects a preset and resource group and clicks Deploy. This makes the documented pre-populated fields misleading for the VFolder deployment path.
## Pre-Populated Launcher Fields

When you choose the manual-deploy path, the deployment launcher opens with every field pre-filled from the selected preset:

- Image, runtime variant, and resource group.
- Resource slots, shared memory, and resource options.
- Cluster mode and cluster size.
- Startup command and environment variables.
- Replica count, revision history limit, and **Open to Public** visibility.
- Auto-selected resource preset, which is preserved across the launcher's initial-value resolution.

packages/backend.ai-webui-docs/src/ko/model_serving/deployment_presets.md:123

  • This section describes a manual-deploy launcher being pre-filled from the selected preset, but the VFolder preset flow implemented in VFolderDeployModal does not open a deployment launcher. It either auto-deploys directly, or shows a small modal where the user selects a preset and resource group and clicks Deploy. This makes the documented pre-populated fields misleading for the VFolder deployment path.
## 자동 채워지는 런처 필드

수동 배포 경로를 선택하면 다음과 같은 모든 필드가 선택한 프리셋의 값으로 자동으로 채워진 상태로 배포 런처가 열립니다.

- 이미지, 런타임 변형, 자원 그룹.
- 자원 슬롯, 공유 메모리, 자원 옵션.
- 클러스터 모드와 클러스터 크기.
- 시작 명령과 환경 변수.
- 레플리카 수, 리비전 기록 보관 수, **Open to Public** 공개 여부.
- 자동으로 선택된 자원 프리셋. 런처의 초기값 해석 과정에서도 그대로 유지됩니다.

packages/backend.ai-webui-docs/src/ja/model_serving/deployment_presets.md:123

  • This section describes a manual-deploy launcher being pre-filled from the selected preset, but the VFolder preset flow implemented in VFolderDeployModal does not open a deployment launcher. It either auto-deploys directly, or shows a small modal where the user selects a preset and resource group and clicks Deploy. This makes the documented pre-populated fields misleading for the VFolder deployment path.
## 事前入力されるランチャー項目

手動デプロイの経路を選択すると、次のような項目がすべて選択したプリセットの値で事前入力された状態でデプロイランチャーが開きます。

- イメージ、ランタイムバリアント、リソースグループ。
- リソーススロット、共有メモリ、リソースオプション。
- クラスターモードとクラスターサイズ。
- 起動コマンドと環境変数。
- レプリカ数、リビジョン履歴の保持数、**Open to Public** 公開可否。
- 自動選択されたリソースプリセット。ランチャーの初期値解決処理を経てもそのまま維持されます。

packages/backend.ai-webui-docs/src/th/model_serving/deployment_presets.md:123

  • This section describes a manual-deploy launcher being pre-filled from the selected preset, but the VFolder preset flow implemented in VFolderDeployModal does not open a deployment launcher. It either auto-deploys directly, or shows a small modal where the user selects a preset and resource group and clicks Deploy. This makes the documented pre-populated fields misleading for the VFolder deployment path.
## ฟิลด์ของ Launcher ที่ถูกเติมไว้ล่วงหน้า

เมื่อคุณเลือกเส้นทาง Manual deploy, deployment launcher จะเปิดขึ้นโดยเติมทุกฟิลด์จากพรีเซ็ตที่เลือกล่วงหน้า ดังนี้:

- อิมเมจ, runtime variant และ resource group
- Resource slots, หน่วยความจำที่แชร์ และตัวเลือกทรัพยากร
- Cluster mode และขนาดคลัสเตอร์
- Startup command และ environment variables
- จำนวน replica, จำนวน revision ที่เก็บไว้ และค่า **Open to Public**
- resource preset ที่ถูกเลือกอัตโนมัติ และจะคงอยู่ตลอดกระบวนการกำหนดค่าเริ่มต้นของ launcher

packages/backend.ai-webui-docs/src/en/model_serving/deployment_presets.md:112

  • The selected preset/detail state for this flow is not preserved in the URL. In the implemented VFolder flow, presetDetailId is local React state and the detail modal is opened from the info button; there is no URLSearchParams integration for sharing a preset-detail URL. This note documents a deep-linking behavior users will not actually get.
:::note
The active preset, tab key, and other navigation state are preserved in the URL via `URLSearchParams`. You can share a link to a specific preset's detail view, and the recipient lands on the same screen.
:::

packages/backend.ai-webui-docs/src/ko/model_serving/deployment_presets.md:112

  • The selected preset/detail state for this flow is not preserved in the URL. In the implemented VFolder flow, presetDetailId is local React state and the detail modal is opened from the info button; there is no URLSearchParams integration for sharing a preset-detail URL. This note documents a deep-linking behavior users will not actually get.
:::note
선택된 프리셋과 탭 키 등 내비게이션 상태는 `URLSearchParams`를 통해 URL에 보존됩니다. 특정 프리셋 상세 화면의 링크를 공유하면 받는 사람도 동일한 화면에서 시작할 수 있습니다.
:::

packages/backend.ai-webui-docs/src/ja/model_serving/deployment_presets.md:112

  • The selected preset/detail state for this flow is not preserved in the URL. In the implemented VFolder flow, presetDetailId is local React state and the detail modal is opened from the info button; there is no URLSearchParams integration for sharing a preset-detail URL. This note documents a deep-linking behavior users will not actually get.
:::note
選択中のプリセットやタブキーなどのナビゲーション状態は `URLSearchParams` を介して URL に保持されます。特定のプリセット詳細画面のリンクを共有すれば、受け取った相手も同じ画面から開始できます。
:::

packages/backend.ai-webui-docs/src/th/model_serving/deployment_presets.md:112

  • The selected preset/detail state for this flow is not preserved in the URL. In the implemented VFolder flow, presetDetailId is local React state and the detail modal is opened from the info button; there is no URLSearchParams integration for sharing a preset-detail URL. This note documents a deep-linking behavior users will not actually get.
:::note
พรีเซ็ตที่เลือก, key ของแท็บ และสถานะนำทางอื่น ๆ จะถูกเก็บไว้ใน URL ผ่าน `URLSearchParams` คุณสามารถแชร์ลิงก์ของหน้ารายละเอียดพรีเซ็ต และผู้รับจะเปิดไปยังหน้าจอเดียวกันได้
:::

packages/backend.ai-webui-docs/src/en/model_serving/deployment_presets.md:140

  • This documents tag chips on the preset lists, but the implemented deployment preset list does not expose tags: AdminDeploymentPresetNodes does not query or render a tags field, and AdminDeploymentPresetListPage only filters by name and runtime variant. The clickable DeploymentTagChips component is used for model deployments, not deployment presets, so these instructions point users to functionality that is not present.
## Filtering by Tags

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.

![](images/deployment_preset_tag_filter.png)
<!-- TODO: Capture screenshot of the deployment preset list filtered by a tag chip -->

1. Locate a preset row that has the tag you want to filter by.
2. Click the tag chip on that row.
3. The list refreshes to show only presets that include the selected tag. The active filter is reflected in the filter bar; clear it to return to the full list.

packages/backend.ai-webui-docs/src/ko/model_serving/deployment_presets.md:140

  • This documents tag chips on the preset lists, but the implemented deployment preset list does not expose tags: AdminDeploymentPresetNodes does not query or render a tags field, and AdminDeploymentPresetListPage only filters by name and runtime variant. The clickable DeploymentTagChips component is used for model deployments, not deployment presets, so these instructions point users to functionality that is not present.
## 태그로 필터링하기

사용자용 프리셋 목록과 관리자용 프리셋 목록 모두 **클릭 가능한 태그 칩**을 지원합니다. 클릭한 태그를 공유하는 프리셋만 표시되도록 목록이 필터링됩니다.

![](images/deployment_preset_tag_filter.png)
<!-- TODO: Capture screenshot of the deployment preset list filtered by a tag chip -->

1. 필터링하려는 태그가 표시된 프리셋 행을 찾습니다.
2. 해당 행의 태그 칩을 클릭합니다.
3. 선택한 태그가 포함된 프리셋만 표시되도록 목록이 갱신됩니다. 활성화된 필터는 필터 바에 표시되며, 필터를 해제하면 전체 목록으로 돌아갑니다.

packages/backend.ai-webui-docs/src/ja/model_serving/deployment_presets.md:140

  • This documents tag chips on the preset lists, but the implemented deployment preset list does not expose tags: AdminDeploymentPresetNodes does not query or render a tags field, and AdminDeploymentPresetListPage only filters by name and runtime variant. The clickable DeploymentTagChips component is used for model deployments, not deployment presets, so these instructions point users to functionality that is not present.
## タグでフィルターする

ユーザー向け/管理者向けのいずれのプリセット一覧でも、**クリック可能なタグチップ** がサポートされており、クリックしたタグを共有するプリセットだけを表示するよう一覧をフィルターできます。

![](images/deployment_preset_tag_filter.png)
<!-- TODO: Capture screenshot of the deployment preset list filtered by a tag chip -->

1. フィルターしたいタグが付いているプリセット行を見つけます。
2. その行のタグチップをクリックします。
3. 選択したタグを含むプリセットだけが表示されるよう一覧が更新されます。アクティブなフィルターはフィルターバーに表示され、解除すると全件表示に戻ります。

packages/backend.ai-webui-docs/src/th/model_serving/deployment_presets.md:140

  • This documents tag chips on the preset lists, but the implemented deployment preset list does not expose tags: AdminDeploymentPresetNodes does not query or render a tags field, and AdminDeploymentPresetListPage only filters by name and runtime variant. The clickable DeploymentTagChips component is used for model deployments, not deployment presets, so these instructions point users to functionality that is not present.
## การกรองด้วยแท็ก

ทั้งรายการพรีเซ็ตของผู้ใช้และรายการพรีเซ็ตของผู้ดูแลระบบรองรับ **ชิปแท็กที่คลิกได้** ซึ่งจะกรองรายการให้แสดงเฉพาะพรีเซ็ตที่ใช้แท็กเดียวกัน

![](images/deployment_preset_tag_filter.png)
<!-- TODO: Capture screenshot of the deployment preset list filtered by a tag chip -->

1. ค้นหาแถวพรีเซ็ตที่มีแท็กที่คุณต้องการใช้กรอง
2. คลิกชิปแท็กในแถวนั้น
3. รายการจะรีเฟรชโดยแสดงเฉพาะพรีเซ็ตที่มีแท็กที่เลือกไว้ ฟิลเตอร์ที่ใช้งานอยู่จะแสดงในแถบตัวกรอง คลิกเพื่อล้างฟิลเตอร์และกลับไปยังรายการทั้งหมด

packages/backend.ai-webui-docs/src/en/model_serving/deployment_presets.md:49

  • The admin preset form is not opened in a dialog. The list page's create action navigates to /admin-deployments/deployment-presets/new, which renders AdminDeploymentPresetSettingPage as a full page. Calling this a Create Preset dialog will mislead users about where the form appears.
1. Click the **Create Preset** button at the top right of the preset list.
2. Fill in the fields in the *Create Preset* dialog. The dialog is organized into the following sections:

packages/backend.ai-webui-docs/src/ko/model_serving/deployment_presets.md:49

  • The admin preset form is not opened in a dialog. The list page's create action navigates to /admin-deployments/deployment-presets/new, which renders AdminDeploymentPresetSettingPage as a full page. Calling this a create dialog will mislead users about where the form appears.
1. 프리셋 목록 우측 상단의 **프리셋 생성** 버튼을 클릭합니다.
2. *프리셋 생성* 대화 상자의 각 섹션을 입력합니다.

packages/backend.ai-webui-docs/src/ja/model_serving/deployment_presets.md:49

  • The admin preset form is not opened in a dialog. The list page's create action navigates to /admin-deployments/deployment-presets/new, which renders AdminDeploymentPresetSettingPage as a full page. Calling this a create dialog will mislead users about where the form appears.
1. プリセット一覧の右上にある **プリセットを作成** ボタンをクリックします。
2. *プリセットを作成* ダイアログの各セクションに入力します。

packages/backend.ai-webui-docs/src/th/model_serving/deployment_presets.md:49

  • The admin preset form is not opened in a dialog. The list page's create action navigates to /admin-deployments/deployment-presets/new, which renders AdminDeploymentPresetSettingPage as a full page. Calling this a create dialog will mislead users about where the form appears.
1. คลิกปุ่ม **สร้างค่าตั้งล่วงหน้า** ที่มุมขวาบนของรายการพรีเซ็ต
2. กรอกฟิลด์ในไดอะล็อก *สร้างค่าตั้งล่วงหน้า* ซึ่งจัดเป็นส่วนต่าง ๆ ดังนี้:

packages/backend.ai-webui-docs/src/en/model_serving/deployment_presets.md:80

  • Editing a preset also navigates to the full-page AdminDeploymentPresetSettingPage (/admin-deployments/deployment-presets/:presetId/edit) rather than opening an edit dialog. The documented dialog workflow and modal screenshot do not match the implemented UI.
1. From the preset list, open the action menu on the preset row (or open the preset's detail view) and select **Edit Preset**.
2. The *Edit Preset* dialog opens with the preset's current values pre-filled. The available sections are identical to the *Create Preset* dialog.
3. Adjust the fields as needed, then click **Edit Preset** to save your changes.

![](images/deployment_preset_edit_modal.png)

packages/backend.ai-webui-docs/src/ko/model_serving/deployment_presets.md:80

  • Editing a preset also navigates to the full-page AdminDeploymentPresetSettingPage (/admin-deployments/deployment-presets/:presetId/edit) rather than opening an edit dialog. The documented dialog workflow and modal screenshot do not match the implemented UI.
1. 프리셋 목록의 행 작업 메뉴(또는 프리셋 상세 화면)에서 **프리셋 편집**을 선택합니다.
2. *프리셋 편집* 대화 상자가 현재 값으로 채워진 상태로 열립니다. 사용 가능한 섹션은 *프리셋 생성* 대화 상자와 동일합니다.
3. 필요한 값을 수정한 뒤 **프리셋 편집** 버튼을 클릭하여 저장합니다.

![](images/deployment_preset_edit_modal.png)

packages/backend.ai-webui-docs/src/ja/model_serving/deployment_presets.md:80

  • Editing a preset also navigates to the full-page AdminDeploymentPresetSettingPage (/admin-deployments/deployment-presets/:presetId/edit) rather than opening an edit dialog. The documented dialog workflow and modal screenshot do not match the implemented UI.
1. プリセット一覧の行アクションメニュー(またはプリセット詳細画面)から **プリセットを編集** を選択します。
2. *プリセットを編集* ダイアログが現在の値で事前に入力された状態で開きます。使用可能なセクションは *プリセットを作成* ダイアログと同じです。
3. 必要な値を変更し、**プリセットを編集** ボタンをクリックして保存します。

![](images/deployment_preset_edit_modal.png)

packages/backend.ai-webui-docs/src/th/model_serving/deployment_presets.md:80

  • Editing a preset also navigates to the full-page AdminDeploymentPresetSettingPage (/admin-deployments/deployment-presets/:presetId/edit) rather than opening an edit dialog. The documented dialog workflow and modal screenshot do not match the implemented UI.
1. จากรายการพรีเซ็ต ให้เปิดเมนูการกระทำของแถวพรีเซ็ต (หรือเปิดหน้ารายละเอียดของพรีเซ็ต) แล้วเลือก **แก้ไขค่าตั้งล่วงหน้า**
2. ไดอะล็อก *แก้ไขค่าตั้งล่วงหน้า* จะเปิดขึ้นพร้อมเติมค่าปัจจุบันของพรีเซ็ตไว้ล่วงหน้า ส่วนต่าง ๆ ที่ใช้ได้จะเหมือนกับไดอะล็อก *สร้างค่าตั้งล่วงหน้า*
3. ปรับค่าตามต้องการ แล้วคลิก **แก้ไขค่าตั้งล่วงหน้า** เพื่อบันทึก

![](images/deployment_preset_edit_modal.png)

Comment thread packages/backend.ai-webui-docs/src/en/model_serving/deployment_presets.md Outdated
Comment thread packages/backend.ai-webui-docs/src/ko/model_serving/deployment_presets.md Outdated
Comment thread packages/backend.ai-webui-docs/src/ja/model_serving/deployment_presets.md Outdated
Comment thread packages/backend.ai-webui-docs/src/th/model_serving/deployment_presets.md Outdated
@agatha197 agatha197 force-pushed the 05-15-docs_model-serving_add_deployment_preset_management_documentation branch from 6bcfb43 to 7f47284 Compare May 18, 2026 03:54
@agatha197 agatha197 force-pushed the 05-15-docs_model-serving_update_for_deployment-only_create_modal_revision_ux_and_detail_page_polish branch from ca4ddc5 to 1b25189 Compare May 18, 2026 03:54
@agatha197 agatha197 changed the base branch from 05-15-docs_model-serving_update_for_deployment-only_create_modal_revision_ux_and_detail_page_polish to graphite-base/7444 May 18, 2026 05:20
@agatha197 agatha197 force-pushed the graphite-base/7444 branch from 1b25189 to accb898 Compare May 18, 2026 05:42
@agatha197 agatha197 force-pushed the 05-15-docs_model-serving_add_deployment_preset_management_documentation branch from 7f47284 to 0e1a8dc Compare May 18, 2026 05:42
@agatha197 agatha197 changed the base branch from graphite-base/7444 to 05-15-docs_model-serving_update_for_deployment-only_create_modal_revision_ux_and_detail_page_polish May 18, 2026 05:42
@agatha197 agatha197 force-pushed the 05-15-docs_model-serving_add_deployment_preset_management_documentation branch from 0e1a8dc to a98625c Compare May 18, 2026 06:29
@agatha197 agatha197 force-pushed the 05-15-docs_model-serving_update_for_deployment-only_create_modal_revision_ux_and_detail_page_polish branch from accb898 to 47bc665 Compare May 18, 2026 06:29
@agatha197 agatha197 changed the base branch from 05-15-docs_model-serving_update_for_deployment-only_create_modal_revision_ux_and_detail_page_polish to 05-18-docs_model-serving_capture_endpoint_detail_ready-alert_and_replica-filter_screenshots May 18, 2026 07:23
@agatha197 agatha197 force-pushed the 05-18-docs_model-serving_capture_endpoint_detail_ready-alert_and_replica-filter_screenshots branch from a9a6165 to c26480f Compare May 18, 2026 07:25
Part of the recent main-branch docs catch-up plan (Work Item 11).

New page documenting the Deployment Preset feature introduced over Q1–Q2 2026:

- FR-2750 (#7091) feature spec
- FR-2761 (#7125) admin create / edit / delete UI
- FR-2762 (#7127) preset detail view in VFolderDeployModal
- FR-2801 (#7224) pre-populate launcher fields from preset
- FR-2805 (#7233) URLSearchParams in preset navigation
- FR-2827 (#7274) clickable deployment tags filter the list
- FR-2810 (#7242) batch image canonical names on admin preset list
- FR-2773 (#7153) preserve auto-selected resourcePresetId

New sections:
1. What is a Deployment Preset?
2. (Admin) Manage Deployment Presets — list, filter, create, edit, delete (typed-confirm)
3. Using a Preset when Deploying a Model — preset detail, auto/manual deploy paths
4. Pre-populated Launcher Fields
5. Filtering by Tags

Also adds book.config.yaml navigation entries under the Model Serving category in all 4 languages.

Updated in all 4 languages (en/ko/ja/th). Screenshots flagged with TODO markers for separate capture. Linked from model_serving.md (PR B) so PR B's cross-references now resolve.
…(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().
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size:XL 500~ LoC

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants