diff --git a/docs/tutorials/3.admin/assets-files.md b/docs/tutorials/3.admin/assets-files.md index 7581afde3..9daa1ef0e 100644 --- a/docs/tutorials/3.admin/assets-files.md +++ b/docs/tutorials/3.admin/assets-files.md @@ -2,13 +2,15 @@ ## Introduction -Files in DIAL are arbitrary binary or text assets (JSON, CSV, PDF, images, etc.) your models and applications can reference at runtime. +Files in DIAL are arbitrary binary or text assets (JSON, CSV, PDF, images, etc.) which AI models and/or applications can reference at runtime. Files in DIAL can be stored in BLOB storage or a local file system. + +Files are considered to be a protected resource. Refer to [Access Control](/docs/platform/3.core/2.access-control-intro.md) to learn how protected resources are handled in DIAL. ## Main Screen -In Files, you can manage all files in the Public folder. +In Files, you can view and manage all files located the **Public** folder in the DIAL's file system. Files in the Public folder are files published with applications by end users or manually uploaded by administrators. -> Refer to [Access Control](/docs/platform/3.core/2.access-control-intro.md) to lean more about Private and Public logical spaces for objects storage in DIAL. +> **Note**: This screen, does not give access to private files of users. ![ ](img/img_35.png) diff --git a/docs/tutorials/3.admin/assets-prompts.md b/docs/tutorials/3.admin/assets-prompts.md index 17c10243b..b6f713a91 100644 --- a/docs/tutorials/3.admin/assets-prompts.md +++ b/docs/tutorials/3.admin/assets-prompts.md @@ -2,15 +2,15 @@ ## About Prompts -A prompt is an instruction, a question, or a message that a user provides to a language model to receive an answer. Prompts can also contain constraints or requirements. They help the model understand the task at hand and the types of responses that are expected. You can use prompts as templates for your messages, instructions to the model, or to encourage the model to generate specific types of content. In DIAL, you can create prompts beforehand and reuse them in one or several conversations. +Prompts in DIAL can be stored in BLOB storage or a local file system. -> Refer to [DIAL Chat User Guide](/docs/tutorials/0.user-guide.md#prompts) to learn more about prompts and DIAL Chat features. +Prompts are considered to be a protected resource. Refer to [Access Control](/docs/platform/3.core/2.access-control-intro.md) to learn how protected resources are handled in DIAL. -## Main Screen +> Refer to [DIAL Chat User Guide](/docs/tutorials/0.user-guide.md#prompts) to learn more about prompts. -All prompts published by users get into the Public folder. In the Prompts section, you can manage all system and user prompt templates available in the Public folder. All Here, you can also arrange prompts into folders, version them, and then use them in applications or chats. +## Main Screen -> Refer to [Access Control](/docs/platform/3.core/2.access-control-intro.md) to lean more about Private and Public logical spaces for objects storage in DIAL. +In Prompts, you can access and manage all prompts in the Public folder. Prompts get to the Public folder if published by users or added by administrators. ![ ](img/img_32.png) diff --git a/docs/tutorials/3.admin/assets-toolsets.md b/docs/tutorials/3.admin/assets-toolsets.md index 32dd86752..d6dda961c 100644 --- a/docs/tutorials/3.admin/assets-toolsets.md +++ b/docs/tutorials/3.admin/assets-toolsets.md @@ -2,15 +2,13 @@ ## Introduction -Toolsets in DIAL are connections with MCP servers that you can use as tools in [Quick Apps 2.0](/docs/video%20demos/2.Applications/5.quick-apps.md). +Toolsets in DIAL are connections with MCP servers that can be used as tools by any internal or external application to perform specific actions. Refer to [Video Demo](/docs/video%20demos/2.Applications/5.quick-apps.md) to watch how tools are used in [DIAL Quick Apps 2.0](/docs/platform/3.core/7.apps.md#quick-apps-20). -## Main Screen - -On the main screen, you can find all publicly-available Toolsets that have either been published by DIAL users or added via a direct modification to [DIAL Core's dynamic settings](https://github.com/epam/ai-dial-core/blob/development/docs/dynamic-settings/toolsets.md). +Toolsets are considered to be a protected resource. Refer to [Access Control](/docs/platform/3.core/2.access-control-intro.md) to learn how protected resources are handled in DIAL. -Publicly-available toolsets can be accessed via [DIAL Core API](https://dialx.ai/dial_api#tag/Deployment-listing/operation/getToolSets) or [DIAL Marketplace](/docs/platform/4.chat/1.marketplace.md) by all authorized users and apps. +## Main Screen -> Refer to [Access Control](/docs/platform/3.core/2.access-control-intro.md) to lean more about Private and Public logical spaces for objects storage in DIAL. +On the main screen, you can find all Toolsets located in the Public folder. Such toolsets have either been published by DIAL users or added by administrators. ![ ](img/131.png) diff --git a/docs/tutorials/3.admin/deployments-images.md b/docs/tutorials/3.admin/deployments-images.md index 176292862..d62fd7e40 100644 --- a/docs/tutorials/3.admin/deployments-images.md +++ b/docs/tutorials/3.admin/deployments-images.md @@ -10,22 +10,22 @@ On the main screen, you can see all the available and add new images for MCP Ser ![](img/deployment_images.png) -##### Images Grid - -| Column | Description | -|----------------|--------------------------------------------------------------| -| ID | Unique identifier of the image. | -| Version | Version of the image. | -| Name | Name of the image. | -| Description | Brief description of the image. | -| Type | Type of the image (MCP or Interceptor). | -| Source | Image or a Source code.| -| Status | Current status of the image. | -| Update time | Date and time when the image was last updated. | -| Create time | Date and time when the image was created. | -| Topics | List of topics associated with the image. | -| Transport type | Transport type used by the MCP image:
- **Remote** (HTTP/SSE)
- **Local** (STDIO).| -| Actions | Buttons to manage the selected image:
- **Delete**: click to remove the image.
- **Duplicate**: click to create a copy of the image.
- **Open in a new tab**: click to open image properties in a new tab in your browser. | +##### Images grid + +| Column | Description | +|--------|-------------| +| ID | Unique identifier of the image. | +| Version | Version of the image. | +| Name | Name of the image. | +| Description | Brief description of the image. | +| Type | Type of the image (MCP or Interceptor). | +| Source | Image or a Source code. | +| Status | Current status of the image. | +| Update time | Date and time when the image was last updated. | +| Create time | Date and time when the image was created. | +| Topics | List of topics associated with the image. | +| Transport type | Transport type used by the MCP image:
- **Remote** (HTTP/SSE)
- **Local** (STDIO). | +| Actions | Buttons to manage the selected image:
- **Delete**: Use to remove the image.
- **Duplicate**: Use to create a copy of the image.
- **Open in a new tab**: Use to open image properties in a new tab in your browser. | ## Add Image @@ -36,19 +36,27 @@ On the main screen, you can add new images for MCP Servers and Interceptors. 1. Click the **+Add** button on the main screen to open the **Adding Image** form. 2. Populate the required fields and click **Add** to add the image. -| Field | Required |Description | -|----------------|-----------|---------------------------------------------------| -| Name | Yes | Name of the image. | -| Description | No | Brief description of the image. | -|Version | Yes |Version of the image. | -| Type | Yes |Type of the image (MCP or Interceptor). | -|Source type| Conditional | **Note**: Required for MCP type.
The source type of the Docker image:
- **Docker Image**
- **Source Code**| -|Docker image URI| Conditional| URI of the Docker image.
Applies to both MCP (if Source type = Docker image) and Interceptor types.| -|Source code repository parameters| Conditional |Applies if Type = MCP Image and Source type = Source code .
- **Repo URL**: a source code repository URL. **Required**
- **Branch name**: the name of the branch in the source code repository.
- **SHA**: the SHA in the source code repository.| +| Field | Required | Description | +|-------|----------|-------------| +| Name | Yes | Name of the image. | +| Description | No | Brief description of the image. | +| Version | Yes | Version of the image. | +| Type | Yes | Type of the image (MCP or Interceptor). | +| Source type | Conditional | **Note**: Required for MCP type.
The source type of the Docker image:
- **Docker Image**
- **Source Code** | +| Docker image URI | Conditional | URI of the Docker image.
Applies to both MCP (if Source type = Docker image) and Interceptor types. | +| Source code repository parameters | Conditional | Applies if Type = MCP Image and Source type = Source code .
- **Repo URL**: a source code repository URL. **Required**
- **Branch name**: the name of the branch in the source code repository.
- **SHA**: the SHA in the source code repository. | ![ ](img/add_image.png) -## Configuration Screen +## Global firewall + +On the main screen, click **Global firewall** to define a list of domain names allowed to access all deployed images. This is a security feature that restricts incoming requests, so only trusted domains (such as your company’s website or specific client applications) have access. + +**Domain name requirements**: Enter the domain name without protocol, e.g., github.com. Each domain must have at least one dot, labels can include letters, numbers, and hyphens (1–63 chars, not starting or ending with a hyphen), and the top-level domain must be at least 2 letters. + +![ ](img/images_global_firewall.png) + +## Configuration Click any image from the main screen to open its configuration screen. @@ -58,12 +66,12 @@ On the configuration screen, you can view and edit the selected image settings. In the header of the Configuration screen, you can find the following action buttons: -| Action | Description | -|----------------|--------------------------------------------------------------| -| Version| Click to create a new image version or display configuration of a selected version.| -| Create Interceptor/MCP Container | Enabled for the installed images.
Click to create a new [MCP](/docs/tutorials/3.admin/deployments-mcp.md) or [Interceptor](/docs/tutorials/3.admin/deployments-interceptors.md) container based on the selected image. | -| Install | Enabled for not installed images.
Click to install the selected version of an image. | -| Delete | Click to delete the selected image. | +| Action | Description | +|--------|-------------| +| Version | Click to create a new image version or display configuration of a selected version. | +| Create Interceptor/MCP Container | Enabled for the installed images.
Click to create a new [MCP](/docs/tutorials/3.admin/deployments-mcp.md) or [Interceptor](/docs/tutorials/3.admin/deployments-interceptors.md) container based on the selected image. | +| Install | Enabled for not installed images.
Click to install the selected version of an image. | +| Delete | Click to delete the selected image. **Note**: Deleted image will effect the related containers. | ![ ](img/image_actions.png) @@ -71,22 +79,22 @@ In the header of the Configuration screen, you can find the following action but In the Properties tab, you can preview and modify selected image's basic properties. -| Field | Required | Editable | Description | -|----------------|-----------|---------|---------------| -| ID | - | No | Unique identifier of the image. | -|Type| - | No | Type of the image (MCP or Interceptor). | -|Creation Time| - | No | Date and time when the image was created. | -|Updated Time| - | No | Date and time when the image was last updated. | -|Source type|-| No | Source type of the Docker image:
- **Docker Image**
- **Source Code**| -|Status| - | No | Current status of the image. | -| Name | Yes | Yes | Name of the image. | -| Description | No | Yes | Brief description of the image. | -|Maintainer | No | Yes | The maintainer of the image. | -|Topics | No | Yes | List of topics associated with the image. | -|Source type| Conditional | Yes | **Note**: Required for MCP type of image.
The source type of the Docker image:
- **Docker Image**
- **Source Code**| -|Docker image URI| Conditional| Yes| URI of the Docker image.
Applies to both MCP (if Source type = Docker image) and Interceptor types.| -|Source code repository parameters| Conditional | Yes |Applies if Type = MCP Image and Source type = Source code .
- **Repo URL** (required): a source code repository URL.
- **Branch name**: the name of the branch in the source code repository.
- **SHA**: the SHA in the source code repository.
- **Base directory**: the directory path with the Docker file. | -|MCP transport type|Conditional| Yes |Applies only to MCP type of image.
The transport type used by the MCP image:
- **Remote** (HTTP/SSE)
- **Local** (STDIO).| +| Field | Required | Editable | Description | +|-------|----------|----------|-------------| +| ID | - | No | Unique identifier of the image. | +| Type | - | No | Type of the image (MCP or Interceptor). | +| Creation Time | - | No | Date and time when the image was created. | +| Updated Time | - | No | Date and time when the image was last updated. | +| Source type | - | No | Source type of the Docker image:
- **Docker Image**
- **Source Code** | +| Status | - | No | Current status of the image. | +| Name | Yes | Yes | Name of the image. | +| Description | No | Yes | Brief description of the image. | +| Maintainer | No | Yes | The maintainer of the image. | +| Topics | No | Yes | List of topics associated with the image. | +| Source type | Conditional | Yes | **Note**: Required for MCP type of image.
The source type of the Docker image:
- **Docker Image**
- **Source Code** | +| Docker image URI | Conditional | Yes | URI of the Docker image.
Applies to both MCP (if Source type = Docker image) and Interceptor types. | +| Source code repository parameters | Conditional | Yes | Applies if Type = MCP Image and Source type = Source code .
- **Repo URL** (required): a source code repository URL.
- **Branch name**: the name of the branch in the source code repository.
- **SHA**: the SHA in the source code repository.
- **Base directory**: the directory path with the Docker file. | +| MCP transport type | Conditional | Yes | Applies only to MCP type of image.
The transport type used by the MCP image:
- **Remote** (HTTP/SSE)
- **Local** (STDIO). | ![ ](img/image_properties.png) @@ -94,13 +102,13 @@ In the Properties tab, you can preview and modify selected image's basic propert ![ ](img/image_json_editor.png) -### Build log +### Firewall settings -> This tab is enabled for installed images. +In this section, you can define a list of authorized domain names for the selected image and preview a list of [globally-authorized](#global-firewall) domain names. -The Build Log tab displays the complete output generated during the image build process. Here you can view the step-by-step execution of build instructions, including command outputs, warnings, and errors that occurred during image creation. +**Domain name requirements**: Enter the domain name without protocol, e.g., github.com. Each domain must have at least one dot, labels can include letters, numbers, and hyphens (1–63 chars, not starting or ending with a hyphen), and the top-level domain must be at least 2 letters. -![ ](img/image_build_log.png) +![ ](img/image-firewall.png) ### Related Containers @@ -108,5 +116,22 @@ The Build Log tab displays the complete output generated during the image build The Related Containers tab displays all [MCP](/docs/tutorials/3.admin/deployments-mcp.md) or [Interceptor](/docs/tutorials/3.admin/deployments-interceptors.md) containers related to the selected version of the image. +##### Add containers + +You can link containers to this image or a specific version of it. When you add a container here, it will automatically use the selected image version in its configuration. + +**Note**: Every container must be linked to an image or image version. Once linked, you cannot remove the container from this list—you can only change which image it uses. + +1. Click **Add** to invoke the adding modal. +2. In the modal, you can enable/disable the **Show containers related to this image** toggle to display containers related to this particular image or not. +3. Select one or several containers and click **Apply**. **Important**: Running containers will be restarted with the new image. + ![ ](img/image_related_containers.png) +### Installation log + +> This tab is enabled for installed images. + +The Build Log tab displays the complete output generated during the image build process. Here you can view the step-by-step execution of build instructions, including command outputs, warnings, and errors that occurred during image creation. + +![ ](img/image_build_log.png) diff --git a/docs/tutorials/3.admin/deployments-interceptors.md b/docs/tutorials/3.admin/deployments-interceptors.md index b2172e2d5..6b1353a55 100644 --- a/docs/tutorials/3.admin/deployments-interceptors.md +++ b/docs/tutorials/3.admin/deployments-interceptors.md @@ -1,4 +1,4 @@ -# Interceptor Deployments +# Interceptor Containers ## Introduction @@ -20,20 +20,20 @@ In **Interceptor Deployments**, you can manage containers for interceptors withi ![](img/interceptor_deployments.png) -##### Interceptor Containers Grid +##### Interceptor containers grid | Column | Description | |--------|-------------| -| Display Name | Name of the interceptor container rendered in UI. | +| Display Name | Name of the interceptor container rendered on UI. | | Description | Brief description of the interceptor container. | | Interceptor Image | Docker image from which the interceptor container was created. | | Status | Current status of the interceptor container (e.g., Running, Stopped). | | ID | Unique identifier of the interceptor container. | -| Container URL | URL to access the interceptor container. | +| Container URL | URL to access the running interceptor container. | | Maintainer | Maintainer of the interceptor container. | | Create time | Date and time when the interceptor container was created. | | Update time | Date and time when the interceptor container was last updated. | -| Actions | Buttons to manage the selected interceptor container:
- **Open in a new tab**: click to open the container configuration screen in a new tab in your browser.
- **Duplicate**: click to duplicate the interceptor container.
- **Stop/Run**: click to start and stop a container.
- **Delete**: click to remove the container. | +| Actions | Buttons to manage the selected interceptor container:
- **Open in a new tab**: Use to open the container configuration screen in a new tab in your browser.
- **Duplicate**: Use to duplicate the interceptor container.
- **Stop/Run**: Use to start and stop a container.
- **Delete**: Use to remove the container. | ## Create @@ -48,12 +48,14 @@ On the main screen, you can add new interceptor containers based on existing [im ![](img/create_interceptor_container.png) -## Configuration Screen +## Configuration -Click any interceptor container from the main screen to open its configuration screen. +Click any interceptor container on the main screen to open its configuration screen. On the configuration screen, you can view and edit the selected interceptor container settings, start and stop the container, view logs and events, or delete the container. +> **Note**: Configuration fields are disabled when the container is in a transition state (launching or stopping). + ### Actions In the header of the Configuration screen, you can find the following action buttons: @@ -62,7 +64,7 @@ In the header of the Configuration screen, you can find the following action but |------- |-------------| | Create Interceptor | Available for running containers.
Click to create a new [interceptor](/docs/tutorials/3.admin/entities-interceptors.md) using this selected interceptor container. | | Run/Stop | Click to start or stop the interceptor container. | -| Delete | Click to delete the interceptor container. | +| Delete | Click to delete the interceptor container. **Note**: This will effect interceptors created based on the deleted container. | ![](img/interceptor_container_actions.png) @@ -72,8 +74,8 @@ You can use a **running** interceptor container to create a new interceptor in D 1. In the Configuration screen of the running interceptor container, click the **Create Interceptor** button in the header. 2. In the Create Interceptor dialog, fill in the form fields: - - **ID**: Unique identifier for the interceptor. - - **Display Name**: Enter a name for the interceptor. + - **ID**: Unique identifier for the interceptor. Auto-populated according to the selected container. + - **Display Name**: Enter a name for the interceptor. Auto-populated according to the selected container. - **Description**: Provide a brief description of the interceptor. 3. Click the **Create** button to submit the form and create the interceptor. Repeat these steps to create more interceptors if needed. @@ -83,23 +85,23 @@ You can use a **running** interceptor container to create a new interceptor in D In the Properties tab, you can view and edit the selected interceptor container settings. -##### Fields Description +##### Fields description | Property | Required | Editable | Description | |----------|----------|----------|-------------| | ID | - | No | Unique identifier for the interceptor container. | -| Type | - | No | Type of the interceptor container. | | Interceptor Image | - | No | Docker image from which the interceptor container was created. | | Creation Time | - | No | Date and time when the interceptor container was created. | | Updated Time | - | No | Date and time when the interceptor container was last updated. | | Status | - | No | Current status of the interceptor container (e.g., Running, Stopped). | -| URL | - | No | URL to access the interceptor container. | +| URL | - | No | URL to access the running interceptor container. | +| Restarts | - | No | Restart counter for launching containers. Use to identify crash loops. You can find details in the [Execution Log](#execution-log).| | Display Name | Yes | Yes | Name of the interceptor container rendered in UI. | | Description | No | Yes | Brief description of the interceptor container. | | Maintainer | No | Yes | Maintainer of the interceptor container. | -| Endpoint Configuration | No | Yes | Configuration details for the endpoints exposed by the interceptor container. | -| Environment Variables | No | Yes | Environment variables set for the interceptor container. | -| Resources | No | Yes | Resource limits and requests for the interceptor container. | +| Endpoint Configuration | No | Yes | **Note**: Running container will be redeployed when these settings change.
Configuration details for the endpoints exposed by the interceptor container. | +| Environment Variables | No | Yes | **Note**: Running container will be redeployed when these settings change.
Environment variables set for the interceptor container. | +| Resources | No | Yes | **Note**: Running container will be redeployed when these settings change.
Resource limits and requests for the interceptor container. | ![](img/interceptor_container_properties.png) @@ -107,10 +109,30 @@ In the Properties tab, you can view and edit the selected interceptor container ![ ](img/interceptor_container_json_editor.png) +### Firewall settings + +A whitelist domains setting specifies which domains are allowed to access the interceptor. This is a security feature that restricts incoming requests, so only trusted domains (such as your company’s website or specific client applications) can interact with the interceptor. + +> Refer to [Global Firewall](/docs/tutorials/3.admin/deployments-images.md#global-firewall) to learn how to define authorized domain names for all images. + +**Domain name requirements**: Enter the domain name without protocol, e.g., github.com. Each domain must have at least one dot, labels can include letters, numbers, and hyphens (1–63 chars, not starting or ending with a hyphen), and the top-level domain must be at least 2 letters. + +![ ](img/interceptor_container_firewall.png) + ### Execution log In the Execution Log tab, you can view real-time logs generated by the selected interceptor container. This log provides insights into the container's operations, including any errors or important events that occur during its execution. +In case of issues, health indicators are displayed to help identify problems: + +| Indicator | Description | +|-----------|-------------| +| Restarts | Restart counter for launching containers. Use to identify crash loops. | +| Last restarted at | Timestamp of the last container restart. | +| Last reason | Restart failure reason. | + +![](img/mcp_log.png) + ### Events In the Events tab, you can view a log of significant events related to the selected interceptor container, such as start and stop actions, errors, and other system messages. diff --git a/docs/tutorials/3.admin/deployments-mcp.md b/docs/tutorials/3.admin/deployments-mcp.md index fda3dcd23..d25a89264 100644 --- a/docs/tutorials/3.admin/deployments-mcp.md +++ b/docs/tutorials/3.admin/deployments-mcp.md @@ -1,4 +1,4 @@ -# MCP Deployments +# MCP Containers ## Introduction @@ -20,20 +20,20 @@ On the main screen, you can see a list of all MCP containers along with their cu ![](img/mcp_deployments.png) -##### MCP Containers Grid - -| Column | Description | -|----------------|--------------------------------------------------------------| -| Display Name | Display name of the MCP container rendered in UI. | -| Description | Brief description of the MCP container. | -| MCP Image | Image from which the MCP container was created. | -| Status | Current status of the MCP container (e.g., Running, Stopped). | -|ID | Unique identifier of the MCP container. | -|Container URL | URL to access the MCP container. | -|Maintainer | Maintainer of the MCP container. | -| Create time | Date and time when the MCP container was created. | -|Update time | Date and time when the MCP container was last updated. | -| Actions | Buttons to manage the selected MCP container:
- **Open in a new tab**: click to open the container configuration screen in a new tab in your browser.
- **Duplicate** - click to duplicate the MCP container.
- **Stop/Run**: click to start and stop a container.
- **Delete**: click to remove the container. | +##### MCP containers grid + +| Column | Description | +|--------|-------------| +| Display Name | Name of the MCP container rendered on UI. | +| Description | Brief description of the MCP container. | +| MCP Image | Name of the image from which the MCP container was created. | +| Status | Current status of the MCP container (e.g., Running, Stopped). | +| ID | Unique identifier of the MCP container. | +| Container URL | URL to access the MCP container. | +| Maintainer | Maintainer of the MCP container. | +| Create time | Date and time when the MCP container was created. | +| Update time | Date and time when the MCP container was last updated. | +| Actions | Buttons to manage the selected MCP container:
- **Open in a new tab**: Use to open the container configuration screen in a new tab in your browser.
- **Duplicate**: Use to duplicate the MCP container.
- **Stop/Run**: Use to start and stop a container.
- **Delete**: Use to remove the container. | ## Create @@ -48,30 +48,34 @@ On the main screen, you can add new MCP containers based on existing [images](/d ![](img/create_mcp_container.png) -## Configuration Screen +## Configuration -On the configuration screen, you can view and edit the selected MCP container settings, start and stop the container, view logs and events, or delete the container. +Click any MCP container on the main screen to open its configurations. + +On the configurations screen, you can view and edit the selected MCP container settings, start and stop the container, view logs and events, or delete the container. + +> **Note**: Configuration fields are disabled when the container is in a transition state (launching or stopping). ### Actions In the header of the Configuration screen, you can find the following action buttons: -| Action | Description | -|----------------|--------------------------------------------------------------| -| Create | Available for running containers.
Click to create a new [Toolset](/docs/tutorials/3.admin/entities-toolsets.md) and [Asset Toolset](/docs/tutorials/3.admin/assets-toolsets.md). | -| Run/Stop | Click to start or stop the MCP container. | -| Delete | Click to delete the MCP container. | +| Action | Description | +|--------|-------------| +| Create | Available for running containers.
Click to create a new [Toolset](/docs/tutorials/3.admin/entities-toolsets.md) and [Asset Toolset](/docs/tutorials/3.admin/assets-toolsets.md). | +| Run/Stop | Click to start or stop the MCP container. | +| Delete | Click to delete the MCP container. **Note**: This will effect toolset created based on the deleted container. | ![ ](img/mcp_container_properties_actions.png) ### Create Toolset -You can create a new toolset based on the running MCP container. The created toolset will use the MCP container as its source and appear in the Toolsets list on the [Entities - Toolsets](/docs/tutorials/3.admin/entities-toolsets.md) page. +You can create a new toolset based on the running MCP container. The created toolset will use the MCP container as its source and appear in [Entities/Toolsets](/docs/tutorials/3.admin/entities-toolsets.md). 1. In the Configuration screen of the running MCP container, click the **Create** button in the header and select **Toolset** from the dropdown. 2. In the Create Toolsets dialog, fill in the form fields: - - **ID**: Unique identifier for the toolset. - - **Display Name**: Enter a name for the toolset. + - **ID**: Unique identifier for the toolset. Auto-populated according to the selected MCP container. + - **Display Name**: Enter a name for the toolset. Auto-populated according to the selected MCP container. - **Description**: Provide a brief description of the toolset. 3. Click the **Create** button to submit the form and create the toolset. @@ -79,16 +83,18 @@ You can create a new toolset based on the running MCP container. The created too ### Create Asset Toolset -You can create a new asset toolset based on the running MCP container. The created asset toolset will use the MCP container as its source and appear in the Asset Toolsets list on the [Assets - Toolsets](/docs/tutorials/3.admin/assets-toolsets.md) page. +> Assets are stored in the Public folder in DIAL file system. All authorized users have access to this folder. Objects can be placed in sub-folders, which can have specific access rules applied to them. You can view and manage access rules in [Folders Storage](/docs/tutorials/3.admin/access-management-folders-storage.md). + +You can create a new asset toolset based on the running MCP container. The created asset toolset will use the MCP container as its source and appear in [Assets/Toolsets](/docs/tutorials/3.admin/assets-toolsets.md). 1. In the Configuration screen of the running MCP container, click the **Create** button in the header and select **Asset Toolset** from the dropdown. -2. In the Create Asset Toolsets dialog, fill in the form fields: - - **ID**: Unique identifier for the asset toolset. - - **Display Name**: Enter a name for the asset toolset. +2. In the Create Asset Toolsets dialog, fill in the form fields: + - **Folder Storage**: Select a folder for the asset toolset in the Public storage. + - **ID**: Unique identifier for the asset toolset. Auto-populated according to the selected MCP container. + - **Display Name**: Enter a name for the asset toolset. Auto-populated according to the selected MCP container. - **Version**: Specify a version of the asset toolset. - **Description**: Provide a brief description of the asset toolset. - **External Endpoint**: Specify an external endpoint for the asset toolset. - - **Target folder**: Specify the target folder for the asset toolset. 3. Click the **Create** button to submit the form and create the asset toolset. ![ ](img/create_asset_toolset-deployment.png) @@ -97,23 +103,23 @@ You can create a new asset toolset based on the running MCP container. The creat In the Properties tab, you can preview and modify selected container's basic properties. -##### Fields Description - -| Property | Required | Editable | Description | -|----------------|-----------|----------|------------| -|ID | - | No | Unique identifier of the MCP container.| -|Type | - | No | Type of the MCP container.| -| MCP Image | - | No | Image from which the MCP container was created. Click to open details or navigate to [MCP Images](/docs/tutorials/3.admin/deployments-images.md).| -| Creation Time | - | No | Date and time when the MCP container was created.| -|Updated Time | - | No | Date and time when the MCP container was last updated.| -| Status | - | No | Current status of the MCP container (e.g., Running, Stopped).| -|URL | - | No | The URL to access the MCP container.| -| Display Name | Yes | Yes | Display name of the MCP container rendered in UI. | -| Description | No | Yes | Brief description of the MCP container. | -|Maintainer | No | Yes | Maintainer of the MCP container. | -|Endpoint Configuration| No | Yes | Endpoint configuration of the MCP container:
**Transport**: the transport protocol (HTTP or Server-Sent Events).
**Container endpoint path**: the specific endpoint path where the MCP service is accessible.
**Port**: the network port the container uses.| -|Environment Variables| No | Yes | List of environment variables for the MCP container. You can add, edit, or remove variables as needed.| -|Resources| No | Yes | Resource limits for the MCP container, including CPU and memory allocation. You can adjust these settings based on your requirements.| +##### Fields description + +| Property | Required | Editable | Description | +|----------|----------|----------|-------------| +| ID | - | No | Unique identifier of the MCP container. | +| MCP Image | - | No | Image from which the MCP container was created. Click to open details or navigate to [MCP Images](/docs/tutorials/3.admin/deployments-images.md). | +| Creation Time | - | No | Date and time when the MCP container was created. | +| Updated Time | - | No | Date and time when the MCP container was last updated. | +| Status | - | No | Current status of the MCP container (e.g., Running, Stopped). | +| URL | - | No | The URL to access the running MCP container. | +| Restarts | - | No | Restart counter for launching containers. Use to identify crash loops. You can find details in the [Execution Log](#execution-log). | +| Display Name | Yes | Yes | Display name of the MCP container rendered in UI. | +| Description | No | Yes | Brief description of the MCP container. | +| Maintainer | No | Yes | Maintainer of the MCP container. | +| Endpoint Configuration | No | Yes | **Note**: Running container will be redeployed when these settings change.
Endpoint configuration of the MCP container:
**Transport**: the transport protocol (HTTP (default) or Server-Sent Events).
**Container endpoint path**: the specific endpoint path where the MCP service is accessible.
**Port**: the network port the container uses. | +| Environment Variables | No | Yes | List of environment variables for the MCP container.
You can add, edit, or remove variables as needed.
**Note**: Running container will be redeployed when these settings change. | +| Resources | No | Yes | Resource limits for the MCP container, including CPU and memory allocation. You can adjust these settings based on your requirements.
**Note**: Running container will be redeployed when these settings change. | ![](img/mcp_container_properties.png) @@ -121,6 +127,16 @@ In the Properties tab, you can preview and modify selected container's basic pro ![ ](img/mcp_container_json_editor.png) +### Firewall settings + +A whitelist domains setting in your MCP container configuration specifies which domains are allowed to access the service. This is a security feature that restricts incoming requests, so only trusted domains (such as your company’s website or specific client applications) can interact with the MCP server. + +> Refer to [Global Firewall](/docs/tutorials/3.admin/deployments-images.md#global-firewall) to learn how to define authorized domain names for all images. + +**Domain name requirements**: Enter the domain name without protocol, e.g., github.com. Each domain must have at least one dot, labels can include letters, numbers, and hyphens (1–63 chars, not starting or ending with a hyphen), and the top-level domain must be at least 2 letters. + +![ ](img/mcp-firewall.png) + ### Tools Overview [Tools](https://modelcontextprotocol.io/specification/2025-06-18/server/tools) are specific functions supported by a related MCP server that can be used by clients to perform specific actions (e.g., process, transform, or analyze data flowing through the MCP server). @@ -147,6 +163,16 @@ The Execution Log tab provides real-time visibility into the operations of your ![](img/mcp_container_execution_log.png) +In case of issues, health indicators are displayed to help identify problems: + +| Indicator | Description | +|-----------|-------------| +| Restarts | Restart counter for launching containers. Use to identify crash loops. | +| Last restarted at | Timestamp of the last container restart. | +| Last reason | Restart failure reason. | + +![](img/mcp_log.png) + ### Events The Events tab displays significant state changes and discrete occurrences within your MCP container. Unlike the continuous output in the Execution Log, this tab focuses on specific actions such as container starts, stops, configuration changes, and error conditions. diff --git a/docs/tutorials/3.admin/deployments-models.md b/docs/tutorials/3.admin/deployments-models.md index 5b8d7d3b4..f00dfe7a1 100644 --- a/docs/tutorials/3.admin/deployments-models.md +++ b/docs/tutorials/3.admin/deployments-models.md @@ -28,49 +28,52 @@ On the main screen, you can view existing and add new AI model servings. ##### Model servings grid -|Field|Description| -|---|----| -|Display Name|Name of the model serving rendered on UI.| -|Description|Brief description of the model serving.| -|Source Type|Source type of the model (NIM or Hugging Face).| -|Status|Current status of the model serving.| -|ID|Unique identifier for the model serving.| -|Container URL|URL of the container where the model is hosted.
Available for a running container.| -|Maintainer|Person or team responsible for maintaining the model serving.| -|Create time|Date and time when the model serving was created.| -|Update time|Date and time when the model serving was last updated.| - -## Create - -On the main screen, click the **Create** button to open the Create Model Serving form. +| Field | Description | +|-------|-------------| +| Display Name | Name of the model serving rendered on UI. | +| Description | Brief description of the model serving. | +| Source Type | Source type of the model (NIM or Hugging Face). | +| Status | Current status of the model serving. | +| ID | Unique identifier for the model serving. | +| Container URL | URL of the container where the model is hosted.
Available for a running container. | +| Maintainer | Person or team responsible for maintaining the model serving. | +| Create time | Date and time when the model serving was created. | +| Update time | Date and time when the model serving was last updated. | + +## Create Model Serving + +On the main screen, use the **Create** button to create Hugging Face or NIM model servings. + +![](img/create-model-serving.png) ##### To create a new model serving: -1. Click the **Create** button on the main screen to open the Create Model Serving form. -2. Fill in the required fields in the form: +1. Click the **Create** button on the main screen and select which type of model serving you want to create. +2. Fill in the required fields in the Model Serving form: - **ID**: Unique identifier for the model serving. - **Display Name**: Enter a name for the model serving. - **Description**: Provide a brief description of the model serving. - - **Source Type**: Select the source type (NIM or Hugging Face). - - **Hugging Face Model Name**: Applies to Hugging Face source type. Enter the name of the model from Hugging Face. + - **Hugging Face Model Name**: Applies to Hugging Face source type. Enter the name of the model from Hugging Face or select from the registry. - **Docker Image URI**: Applies to NIM source type. Enter the Docker image URI for the model. 3. Click the **Create** button to submit the form and create the model serving. ![](img/create_model_serving.png) -## Configuration Screen +## Configuration -Click any model serving from the main screen to open its configuration screen. +Click any model serving from the main screen to open its configuration. + +> **Note**: Configuration fields are disabled when the container is in a transition state (launching or stopping). ### Actions In the header of the Configuration screen, you can find the following action buttons: -| Action | Description | -|----------------|--------------------------------------------------------------| -| Create Model | Available for running model servings.
Click to create a new [model deployment](/docs/tutorials/3.admin/entities-models.md) using this selected model serving.| -| Run/Stop | Click to start or stop the selected model serving.| -| Delete | Click to delete the selected model serving.| +| Action | Description | +|--------|-------------| +| Create Model | Available for running model servings.
Click to create a new [model deployment](/docs/tutorials/3.admin/entities-models.md) using this selected model serving. | +| Run/Stop | Click to start or stop the selected model serving. | +| Delete | Click to delete the selected model serving container. **Note**: This will effect model deployments created based on the deleted container. | ![ ](img/model_serving_actions.png) @@ -80,8 +83,8 @@ You can use a **running** model serving container to create a new model deployme 1. In the Configuration screen of the running model serving, click the **Create Model** button in the header. 2. In the Create Model dialog, fill in the form fields: - - **ID**: Unique identifier for the model deployment. - - **Display Name**: Enter a name for the model deployment. + - **ID**: Unique identifier for the model deployment. Auto-populated according to the selected model serving. + - **Display Name**: Enter a name for the model deployment. Auto-populated according to the selected model serving. - **Display Version**: Specify a version of the model deployment. - **Description**: Provide a brief description of the model deployment. 3. Click the **Create** button to submit the form and create the model deployment. Repeat these steps to create more model deployments if needed. @@ -92,24 +95,24 @@ You can use a **running** model serving container to create a new model deployme In the Properties tab, you can view and edit the selected model serving container settings. -| Property | Required | Editable | Description | -|------------------|----------|---------|----------------------------------------------------| -|ID | - |No|Unique identifier of the model serving container. | -|Type| - |No|Container by default.| -|Creation Time| - |No|Date and time when the model serving container was created. | -|Updated Time| - |No|Date and time when the model serving container was last updated. | -|Status| - |No|Current status of the model serving container. | -|URL| - |No|URL of the container where the model is hosted.| -|Display Name | Yes |Yes|Name of the model serving container rendered in UI. | -|Description | No |Yes|Brief description of the model serving container. | -|Maintainer | No |Yes|Person or team responsible for maintaining the model serving container.| -|Source Type| Yes |Yes|Source type of the model (NIM or Hugging Face).| -|Hugging Face model name| Conditional |Yes|Applies to Hugging Face source type.
The name of the model from Hugging Face.| -|Docker Image URI| Conditional |Yes|Applies to NIM source type.
The Docker image URI for the model.| -|Endpoint Configuration| No |Yes|Port configuration for the model serving.| -|Environment Variables| No |Yes|List of environment variables for the model serving.| -|Resources| No |Yes|Resource allocation settings for the model serving (CPU, Memory, GPU).| -|Configuration| No |Additional configuration settings for the model serving container.| +| Property | Required | Editable | Description | +|----------|----------|----------|-------------| +| ID | - | No | Unique identifier of the model serving container. | +| Creation Time | - | No | Date and time when the model serving container was created. | +| Updated Time | - | No | Date and time when the model serving container was last updated. | +| Status | - | No | Current status of the model serving container. | +| Restarts | - | No | Restart counter for launching containers. You can find details in the [Execution Log](#execution-log). | +| URL | - | No | URL of the running container where the model is hosted. | +| Display Name | Yes | Yes | Name of the model serving container rendered in UI. | +| Description | No | Yes | Brief description of the model serving container. | +| Maintainer | No | Yes | Person or team responsible for maintaining the model serving container. | +| Hugging Face model name | Conditional | Yes | Applies to Hugging Face models.
The name of the model from Hugging Face. | +| Docker Image URI | Conditional | Yes | Applies to NIM models.
The Docker image URI for the model. | +| Endpoint Configuration | No | Yes | Port configuration for the model serving.
**Note**: Running container will be redeployed when these settings change. | +| Environment Variables | No | Yes | List of environment variables for the model serving.
**Note**: Running container will be redeployed when these settings change. | +| Resources | No | Yes | Resource allocation settings for the model serving (CPU, Memory, GPU).
**Note**: Running container will be redeployed when these settings change. | +| Configuration | No | Yes | Command that defines the executable and its options to launch the model serving. Arguments provide extra parameters for customization during startup. | +| Autoscaling | No | Yes | **Note**: Autoscaling is available for Hugging Face models.
Parameters to dynamically adjust AI model replicas based on demand.
- **Automatic scale to zero**: Use to define criteria to reduce replicas to zero to save resources.
- **Min and Max Replicas**: Sets the minimum and maximum number of model instances that can run, ensuring availability and controlling costs.
- **Pending requests to trigger autoscaling**: Specifies the number of queued requests required to trigger scaling up, helping maintain performance during traffic spikes. | ![ ](img/model_serving_properties.png) @@ -117,12 +120,32 @@ In the Properties tab, you can view and edit the selected model serving containe ![ ](img/model_serving_json_editor.png) +## Firewall settings + +A whitelist domains setting in your model serving container configuration specifies which domains are allowed to access the model's API or service. This is a security feature that restricts incoming requests, so only trusted domains (such as your company’s website or specific client applications) can interact with the model. + +> Refer to [Global Firewall](/docs/tutorials/3.admin/deployments-images.md#global-firewall) to learn how to define authorized domain names for all images. + +**Domain name requirements**: Enter the domain name without protocol, e.g., github.com. Each domain must have at least one dot, labels can include letters, numbers, and hyphens (1–63 chars, not starting or ending with a hyphen), and the top-level domain must be at least 2 letters. + +![ ](img/model_servings_firewall.png) + ## Execution log -In the Execution Log tab, you can view the logs related to the operations and activities of the selected model serving. +In the Execution Log tab, you can view the logs related to the operations and activities of the selected model serving container. ![ ](img/model_servings_execution_log.png) +In case of issues, health indicators are displayed to help identify problems: + +| Indicator | Description | +|-----------|-------------| +| Restarts | Restart counter for launching containers. Use to identify crash loops. | +| Last restarted at | Timestamp of the last model serving restart. | +| Last reason | Restart failure reason. | + +![ ](img/model_serving_log.png) + ## Events In the Events tab, you can view the event history related to the selected model serving. diff --git a/docs/tutorials/3.admin/img/add_image.png b/docs/tutorials/3.admin/img/add_image.png index ea9262771..feee19402 100644 Binary files a/docs/tutorials/3.admin/img/add_image.png and b/docs/tutorials/3.admin/img/add_image.png differ diff --git a/docs/tutorials/3.admin/img/create-model-serving.png b/docs/tutorials/3.admin/img/create-model-serving.png new file mode 100644 index 000000000..7684d3717 Binary files /dev/null and b/docs/tutorials/3.admin/img/create-model-serving.png differ diff --git a/docs/tutorials/3.admin/img/create_asset_toolset-deployment.png b/docs/tutorials/3.admin/img/create_asset_toolset-deployment.png index cc0d5857a..ed83f93e1 100644 Binary files a/docs/tutorials/3.admin/img/create_asset_toolset-deployment.png and b/docs/tutorials/3.admin/img/create_asset_toolset-deployment.png differ diff --git a/docs/tutorials/3.admin/img/create_interceptor_container.png b/docs/tutorials/3.admin/img/create_interceptor_container.png index 53ddf56e6..6feb8a9c5 100644 Binary files a/docs/tutorials/3.admin/img/create_interceptor_container.png and b/docs/tutorials/3.admin/img/create_interceptor_container.png differ diff --git a/docs/tutorials/3.admin/img/create_interceptor_deployment.png b/docs/tutorials/3.admin/img/create_interceptor_deployment.png index 8c5ca5c98..24f35a38b 100644 Binary files a/docs/tutorials/3.admin/img/create_interceptor_deployment.png and b/docs/tutorials/3.admin/img/create_interceptor_deployment.png differ diff --git a/docs/tutorials/3.admin/img/create_model_deployment.png b/docs/tutorials/3.admin/img/create_model_deployment.png index eb1ca38dc..e1d6280c7 100644 Binary files a/docs/tutorials/3.admin/img/create_model_deployment.png and b/docs/tutorials/3.admin/img/create_model_deployment.png differ diff --git a/docs/tutorials/3.admin/img/create_model_serving.png b/docs/tutorials/3.admin/img/create_model_serving.png index 7e86acf40..2e1a51867 100644 Binary files a/docs/tutorials/3.admin/img/create_model_serving.png and b/docs/tutorials/3.admin/img/create_model_serving.png differ diff --git a/docs/tutorials/3.admin/img/create_toolset_deployment.png b/docs/tutorials/3.admin/img/create_toolset_deployment.png index a6eafb452..5bdd23028 100644 Binary files a/docs/tutorials/3.admin/img/create_toolset_deployment.png and b/docs/tutorials/3.admin/img/create_toolset_deployment.png differ diff --git a/docs/tutorials/3.admin/img/deployment_images.png b/docs/tutorials/3.admin/img/deployment_images.png index 367cbd9b4..95d118add 100644 Binary files a/docs/tutorials/3.admin/img/deployment_images.png and b/docs/tutorials/3.admin/img/deployment_images.png differ diff --git a/docs/tutorials/3.admin/img/image-firewall.png b/docs/tutorials/3.admin/img/image-firewall.png new file mode 100644 index 000000000..29f360594 Binary files /dev/null and b/docs/tutorials/3.admin/img/image-firewall.png differ diff --git a/docs/tutorials/3.admin/img/image_actions.png b/docs/tutorials/3.admin/img/image_actions.png index b1529f340..433dc69e0 100644 Binary files a/docs/tutorials/3.admin/img/image_actions.png and b/docs/tutorials/3.admin/img/image_actions.png differ diff --git a/docs/tutorials/3.admin/img/image_build_log.png b/docs/tutorials/3.admin/img/image_build_log.png index b7e394cc9..f48c33aed 100644 Binary files a/docs/tutorials/3.admin/img/image_build_log.png and b/docs/tutorials/3.admin/img/image_build_log.png differ diff --git a/docs/tutorials/3.admin/img/image_properties.png b/docs/tutorials/3.admin/img/image_properties.png index fc203d454..4d724e706 100644 Binary files a/docs/tutorials/3.admin/img/image_properties.png and b/docs/tutorials/3.admin/img/image_properties.png differ diff --git a/docs/tutorials/3.admin/img/image_related_containers.png b/docs/tutorials/3.admin/img/image_related_containers.png index d9a0c4b88..b2fd646cb 100644 Binary files a/docs/tutorials/3.admin/img/image_related_containers.png and b/docs/tutorials/3.admin/img/image_related_containers.png differ diff --git a/docs/tutorials/3.admin/img/images_global_firewall.png b/docs/tutorials/3.admin/img/images_global_firewall.png new file mode 100644 index 000000000..c71dc1fe4 Binary files /dev/null and b/docs/tutorials/3.admin/img/images_global_firewall.png differ diff --git a/docs/tutorials/3.admin/img/interceptor_container_actions.png b/docs/tutorials/3.admin/img/interceptor_container_actions.png index cd0f7a40a..03b953311 100644 Binary files a/docs/tutorials/3.admin/img/interceptor_container_actions.png and b/docs/tutorials/3.admin/img/interceptor_container_actions.png differ diff --git a/docs/tutorials/3.admin/img/interceptor_container_firewall.png b/docs/tutorials/3.admin/img/interceptor_container_firewall.png new file mode 100644 index 000000000..a045c748b Binary files /dev/null and b/docs/tutorials/3.admin/img/interceptor_container_firewall.png differ diff --git a/docs/tutorials/3.admin/img/interceptor_container_properties.png b/docs/tutorials/3.admin/img/interceptor_container_properties.png index afacf7d6b..1a2a23b8b 100644 Binary files a/docs/tutorials/3.admin/img/interceptor_container_properties.png and b/docs/tutorials/3.admin/img/interceptor_container_properties.png differ diff --git a/docs/tutorials/3.admin/img/interceptor_deployments.png b/docs/tutorials/3.admin/img/interceptor_deployments.png index b9ee6ebe6..d09fd0ff9 100644 Binary files a/docs/tutorials/3.admin/img/interceptor_deployments.png and b/docs/tutorials/3.admin/img/interceptor_deployments.png differ diff --git a/docs/tutorials/3.admin/img/mcp-firewall.png b/docs/tutorials/3.admin/img/mcp-firewall.png new file mode 100644 index 000000000..617d604ce Binary files /dev/null and b/docs/tutorials/3.admin/img/mcp-firewall.png differ diff --git a/docs/tutorials/3.admin/img/mcp_container_events.png b/docs/tutorials/3.admin/img/mcp_container_events.png index c4bb43632..2c19eb65a 100644 Binary files a/docs/tutorials/3.admin/img/mcp_container_events.png and b/docs/tutorials/3.admin/img/mcp_container_events.png differ diff --git a/docs/tutorials/3.admin/img/mcp_container_execution_log.png b/docs/tutorials/3.admin/img/mcp_container_execution_log.png index 50d93a7ae..1da729d80 100644 Binary files a/docs/tutorials/3.admin/img/mcp_container_execution_log.png and b/docs/tutorials/3.admin/img/mcp_container_execution_log.png differ diff --git a/docs/tutorials/3.admin/img/mcp_container_prompts.png b/docs/tutorials/3.admin/img/mcp_container_prompts.png index a4e03c0c6..975781575 100644 Binary files a/docs/tutorials/3.admin/img/mcp_container_prompts.png and b/docs/tutorials/3.admin/img/mcp_container_prompts.png differ diff --git a/docs/tutorials/3.admin/img/mcp_container_properties.png b/docs/tutorials/3.admin/img/mcp_container_properties.png index c69147103..9d3ff035a 100644 Binary files a/docs/tutorials/3.admin/img/mcp_container_properties.png and b/docs/tutorials/3.admin/img/mcp_container_properties.png differ diff --git a/docs/tutorials/3.admin/img/mcp_container_resources.png b/docs/tutorials/3.admin/img/mcp_container_resources.png index 9e3981366..2fecd4db0 100644 Binary files a/docs/tutorials/3.admin/img/mcp_container_resources.png and b/docs/tutorials/3.admin/img/mcp_container_resources.png differ diff --git a/docs/tutorials/3.admin/img/mcp_container_tools.png b/docs/tutorials/3.admin/img/mcp_container_tools.png index 10d2f30e6..bd38707ac 100644 Binary files a/docs/tutorials/3.admin/img/mcp_container_tools.png and b/docs/tutorials/3.admin/img/mcp_container_tools.png differ diff --git a/docs/tutorials/3.admin/img/mcp_deployments.png b/docs/tutorials/3.admin/img/mcp_deployments.png index 03cf09718..76ae8ee74 100644 Binary files a/docs/tutorials/3.admin/img/mcp_deployments.png and b/docs/tutorials/3.admin/img/mcp_deployments.png differ diff --git a/docs/tutorials/3.admin/img/mcp_log.png b/docs/tutorials/3.admin/img/mcp_log.png new file mode 100644 index 000000000..a666debd6 Binary files /dev/null and b/docs/tutorials/3.admin/img/mcp_log.png differ diff --git a/docs/tutorials/3.admin/img/model_serving_actions.png b/docs/tutorials/3.admin/img/model_serving_actions.png index 4dedc2ef5..a3afbd495 100644 Binary files a/docs/tutorials/3.admin/img/model_serving_actions.png and b/docs/tutorials/3.admin/img/model_serving_actions.png differ diff --git a/docs/tutorials/3.admin/img/model_serving_log.png b/docs/tutorials/3.admin/img/model_serving_log.png new file mode 100644 index 000000000..ef6d3645a Binary files /dev/null and b/docs/tutorials/3.admin/img/model_serving_log.png differ diff --git a/docs/tutorials/3.admin/img/model_serving_properties.png b/docs/tutorials/3.admin/img/model_serving_properties.png index 74e7a03f5..600f66a11 100644 Binary files a/docs/tutorials/3.admin/img/model_serving_properties.png and b/docs/tutorials/3.admin/img/model_serving_properties.png differ diff --git a/docs/tutorials/3.admin/img/model_servings.png b/docs/tutorials/3.admin/img/model_servings.png index 12aea6818..532d3b644 100644 Binary files a/docs/tutorials/3.admin/img/model_servings.png and b/docs/tutorials/3.admin/img/model_servings.png differ diff --git a/docs/tutorials/3.admin/img/model_servings_events.png b/docs/tutorials/3.admin/img/model_servings_events.png index 1b74da860..7414232b8 100644 Binary files a/docs/tutorials/3.admin/img/model_servings_events.png and b/docs/tutorials/3.admin/img/model_servings_events.png differ diff --git a/docs/tutorials/3.admin/img/model_servings_execution_log.png b/docs/tutorials/3.admin/img/model_servings_execution_log.png index 7885ff440..cd6aafe9f 100644 Binary files a/docs/tutorials/3.admin/img/model_servings_execution_log.png and b/docs/tutorials/3.admin/img/model_servings_execution_log.png differ diff --git a/docs/tutorials/3.admin/img/model_servings_firewall.png b/docs/tutorials/3.admin/img/model_servings_firewall.png new file mode 100644 index 000000000..8ab29b4d7 Binary files /dev/null and b/docs/tutorials/3.admin/img/model_servings_firewall.png differ diff --git a/docs/video demos/3.Developers/Integrations/8.dial-continue.md b/docs/video demos/3.Developers/Integrations/8.dial-continue.md index ba1ab1740..ebc82b76f 100644 --- a/docs/video demos/3.Developers/Integrations/8.dial-continue.md +++ b/docs/video demos/3.Developers/Integrations/8.dial-continue.md @@ -1,5 +1,5 @@ # AI Code Assistant -https://youtu.be/l0gJM0m_CWw +https://youtu.be/kK8gtZBdzr4 In this video, we will be downloading and configuring an Open Source Copilot-like AI Code Assistant called [Continue](https://www.continue.dev/), and show you how quick and easy it is to integrate with DIAL. This is one of several examples of how DIAL's [Unified API](/docs/video%20demos/3.Developers/3.dial-unified-api.md) and compatibility with industry standards allows for simple integration with many community tools as a results. diff --git a/sidebars.js b/sidebars.js index 4ec18cfca..6ea247cac 100644 --- a/sidebars.js +++ b/sidebars.js @@ -608,18 +608,18 @@ const sidebars = { items: [ { type: 'doc', - id: 'tutorials/admin/deployments-mcp', - label: 'MCP Deployments', + id: 'tutorials/admin/deployments-models', + label: 'Model Servings', }, { type: 'doc', - id: 'tutorials/admin/deployments-interceptors', - label: 'Interceptor Deployments', + id: 'tutorials/admin/deployments-mcp', + label: 'MCP Containers', }, { type: 'doc', - id: 'tutorials/admin/deployments-models', - label: 'Model Servings', + id: 'tutorials/admin/deployments-interceptors', + label: 'Interceptor Containers', }, { type: 'doc',