Skip to content

No jobs UI #911

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Aug 6, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/Researcher/user-interface/trainings.md
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,7 @@ To add a training:
1. Press **Tranings** in the menu.
2. In the *Projects* pane, select the destination project. Use the search box to find projects that are not listed. If you can't find the project, you can create your own, or see your system administrator.
3. In the *Multi-node* pane, choose `Single node` for a single node training, or `Multi-node (distributed)` for distributed training. When you choose `Multi-node`, select a framework that is listed, then select the `multi-node` training configuration by selecting either `Workers & master` or `Workers only`.
4. In the *Templates* pane, select a template from the list. Use the search box to find templates that are not listed. If you can't find the specific template you need, see [Creating a new template](../../admin/admin-ui-setup/templates.md#creating-templates), or see your system administrator.
4. In the *Templates* pane, select a template from the list. Use the search box to find templates that are not listed. If you can't find the specific template you need, see [Creating a new template](../../admin/workloads/templates.md#creating-templates), or see your system administrator.
5. In the *Training name* pane, enter a name for the *Training*, then press continue.
6. Select an environment from the tiles. If your environment is not listed, use the *Search environments* box to find it or press [*New environment*](workspaces/create/create-env.md) to create a new environment. Press to create an environment if needed. In the *Set the connection for your tool(s)*, enter the URL of the tool if a custom URL has been enabled in the selected environment. Use the *Private* toggle to lock access to the tool to only the creator of the environment.

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -87,7 +87,7 @@ ConfigMaps must be created on the cluster before being used within Run:ai. When
## Create a Secret as data source

* A Run:ai project scope which is assigned to that item and all its subsidiaries.
* A *Credentials*. To create a new *Credentials*, see [Configuring Credentials](../../../../admin/admin-ui-setup/credentials-setup.md#configuring-credentials)
* A *Credentials*. To create a new *Credentials*, see [Configuring Credentials](../../../../admin/workloads/credentials-setup.md#configuring-credentials)

!!! Note
You can only choose a project as a scope.
Expand Down
45 changes: 0 additions & 45 deletions docs/admin/admin-ui-setup/overview.md

This file was deleted.

4 changes: 2 additions & 2 deletions docs/admin/authentication/rbac.md
Original file line number Diff line number Diff line change
Expand Up @@ -97,7 +97,7 @@ The table contains the following columns:

To create a new access rule:

1. Press the ![Tools and Settings](../admin-ui-setup/img/tools-and-settings.svg) icon, then *Access rules & Roles*.
1. Press the ![Tools and Settings](img/tools-and-settings.svg) icon, then *Access rules & Roles*.
2. Choose the *ACCESS RULES* tab, then press *NEW ACCESS RULE*.
3. Select a subject type from the dropdown. Choose from:

Expand All @@ -115,5 +115,5 @@ To create a new access rule:

To delete a rule:

1. Press the ![Tools and Settings](../admin-ui-setup/img/tools-and-settings.svg) icon, then *Roles and Access rules*.
1. Press the ![Tools and Settings](img/tools-and-settings.svg) icon, then *Roles and Access rules*.
2. Choose *Access rules*, then select a rule and press *Delete*.
6 changes: 2 additions & 4 deletions docs/admin/authentication/researcher-authentication.md
Original file line number Diff line number Diff line change
Expand Up @@ -170,8 +170,6 @@ You can also submit a Job from the Run:ai User interface and verify that the new

## Test via User Interface

* Open the Run:ai user interface, go to `Jobs`.
* On the top-right, select `Submit Job`.
* Open the Run:ai user interface, go to `Workloads`.
* On the top-right, select `Submit Workload`.

!!! Tip
If you do not see the button or it is disabled, then you either do not have `Researcher` access or the cluster has not been set up correctly. For more information, refer to [user interface overview](../admin-ui-setup/overview.md).
2 changes: 1 addition & 1 deletion docs/admin/runai-setup/cluster-setup/cluster-install.md
Original file line number Diff line number Diff line change
Expand Up @@ -33,7 +33,7 @@ On the next page:
## Verify your cluster's health

* Verify that the cluster status in the Run:ai Control Plane's [Clusters Table](#cluster-table) is `Connected`.
* Go to the [Overview Dashboard](../../admin-ui-setup/dashboard-analysis.md#overview-dashboard) and verify that the number of GPUs on the top right reflects your GPU resources on your cluster and the list of machines with GPU resources appears on the bottom line.
* Go to the [Overview Dashboard](../../performance/dashboard-analysis.md#overview-dashboard) and verify that the number of GPUs on the top right reflects your GPU resources on your cluster and the list of machines with GPU resources appears on the bottom line.
* In case of issues, see the [Troubleshooting guide](../../troubleshooting/cluster-health-check.md).

## Researcher Authentication
Expand Down
13 changes: 13 additions & 0 deletions docs/admin/runai-setup/config/admin-messages.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,13 @@

# Administrator Messages

System administrators can use *Administrator messages* to make announcements to users once they have logged in. These messages typically are used to keep user informed about different aspects of the platform.

To configure an *Administrator message*:

1. Press `Settings | General`.
2. Expand the *Message from administrator* pane.
3. Press *Message*.
4. Enter your message in the text box. Use the formatting tools in the toolbar to add special formatting or links to the message.
5. Enable the `Display "Don't show this again" checkbox on message to users` to allow the users to see the message only once.
6. Press *Publish* when complete.
2 changes: 1 addition & 1 deletion docs/developer/cluster-api/workload-overview-dev.md
Original file line number Diff line number Diff line change
Expand Up @@ -62,7 +62,7 @@ FIELDS:

A Workload can be submitted via various channels:

* The Run:ai [user interface](../../admin/admin-ui-setup/jobs.md).
* The Run:ai user interface.
* The Run:ai command-line interface, via the [runai submit](../../Researcher/cli-reference/runai-submit.md) command.
* The Run:ai [Cluster API](submit-yaml.md).

Expand Down
2 changes: 1 addition & 1 deletion docs/home/data-privacy-details.md
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ Following is a list of platform data items that are sent to the Run:ai cloud.
|---------|---------------|
| Workload Metrics | Workload names, CPU, GPU, and Memory metrics, parameters sent using the `runai submit` command |
| Workload Assets | Workload [Assets](../Researcher/user-interface/workspaces/blocks/building-blocks.md) such as environments, compute resources and data resoruces |
| Resource Credentials | [Credentials](../admin/admin-ui-setup/credentials-setup.md) to cluster resources are stored and encrypted using a SHA-512 algorithm. The encryption is tenant-specific |
| Resource Credentials | [Credentials](../admin/workloads/credentials-setup.md) to cluster resources are stored and encrypted using a SHA-512 algorithm. The encryption is tenant-specific |
| Node Metrics | Node names and IPs, CPU, GPU, and Memory metrics |
| Cluster Metrics | Cluster names, CPU, GPU, and Memory metrics |
| Projects & Departments | Names, quota information |
Expand Down
4 changes: 2 additions & 2 deletions docs/home/whats-new-2-13.md
Original file line number Diff line number Diff line change
Expand Up @@ -65,7 +65,7 @@ This version contains features and fixes from previous versions starting with 2.
**Dashboards**

<!-- RUN9530/9577 New Dashboard for Quota management -->
* Added a new dashboard for **Quota management**, which provides an efficient means to monitor and manage resource utilization within the AI cluster. The dashboard filters the display of resource quotas based on *Departments*, *Projects*, and *Node pools*. For more information, see [Quota management dashboard](../admin/admin-ui-setup/dashboard-analysis.md#quota-management-dashboard).
* Added a new dashboard for **Quota management**, which provides an efficient means to monitor and manage resource utilization within the AI cluster. The dashboard filters the display of resource quotas based on *Departments*, *Projects*, and *Node pools*. For more information, see [Quota management dashboard](../admin/performance/dashboard-analysis.md#quota-management-dashboard).

* Added to the **Overview dashboard**, the ability to filter the cluster by one or more node pools. For more information, see [Node pools](../Researcher/scheduling/using-node-pools.md).

Expand Down Expand Up @@ -110,7 +110,7 @@ The association between workspaces and node pools is done using *Compute resourc
**Credentials**

<!-- RUN-9843/9852 - Allow researcher to create docker registry secrets -->
* Added *Docker registry* to the *Credentials* menu. Users can create docker credentials for use in specific projects for image pulling. To configure credentials, see [Configuring credentials](../admin/admin-ui-setup/credentials-setup.md#configuring-credentials).
* Added *Docker registry* to the *Credentials* menu. Users can create docker credentials for use in specific projects for image pulling. To configure credentials, see [Configuring credentials](../admin/workloads/credentials-setup.md#configuring-credentials).

<!-- RUN-8453/8454/8927 Technical documentation of 'Projects new parameters and options' use existing namespace, status, and more added to projects v2-->

Expand Down
8 changes: 4 additions & 4 deletions docs/home/whats-new-2-15.md
Original file line number Diff line number Diff line change
Expand Up @@ -43,7 +43,7 @@ date: 2023-Dec-3

#### Credentials

* <!-- RUN-10862/RUN-10863 Department as a workspace phase 2 - scope in credentials -->Improved *Credentials* creation. A Run:ai scope can now be added to credentials. For more information, see [Credentials](../admin/admin-ui-setup/credentials-setup.md).
* <!-- RUN-10862/RUN-10863 Department as a workspace phase 2 - scope in credentials -->Improved *Credentials* creation. A Run:ai scope can now be added to credentials. For more information, see [Credentials](../admin/workloads/credentials-setup.md).

#### Environments

Expand All @@ -55,7 +55,7 @@ date: 2023-Dec-3

#### Templates

* <!-- RUN-11692/RUN-11694 Scoping for template-->Added support for Run:ai a *Scope* in the template form. For configuration information, see [Creating templates](../admin/admin-ui-setup/templates.md#creating-templates).
* <!-- RUN-11692/RUN-11694 Scoping for template-->Added support for Run:ai a *Scope* in the template form. For configuration information, see [Creating templates](../admin/workloads/templates.md#creating-templates).

#### Deployments

Expand Down Expand Up @@ -99,9 +99,9 @@ date: 2023-Dec-3

#### Dashboards

* <!-- RUN-12313/12314 - CPU focused dashboards -->To ease the management of AI CPU and cluster resources, a new CPU focused dashboard was added for CPU based environments. The dashboards display specific information for CPU based nodes, node-pools, clusters, or tenants. These dashboards also include additional metrics that are specific to CPU based environments. This will help optimize visual information eliminating the views of empty GPU dashlets. For more information see [CPU Dashboard](../admin/admin-ui-setup/dashboard-analysis.md#cpu-dashboard).
* <!-- RUN-12313/12314 - CPU focused dashboards -->To ease the management of AI CPU and cluster resources, a new CPU focused dashboard was added for CPU based environments. The dashboards display specific information for CPU based nodes, node-pools, clusters, or tenants. These dashboards also include additional metrics that are specific to CPU based environments. This will help optimize visual information eliminating the views of empty GPU dashlets. For more information see [CPU Dashboard](../admin/performance/dashboard-analysis.md#cpu-dashboard).
* <!-- RUN-11421/RUN-11508 Consumption report - Cost and bugs-->Improved the Consumption report interface by moving the Cost settings to the *General* settings menu.
* <!-- RUN-11421/RUN-11508 Consumption report cost and bugs -->Added an additional table to the Consumption dashboard that displays the consumption and cost per department. For more information, see [Consumption dashboard](../admin/admin-ui-setup/dashboard-analysis.md#consumption-dashboard).
* <!-- RUN-11421/RUN-11508 Consumption report cost and bugs -->Added an additional table to the Consumption dashboard that displays the consumption and cost per department. For more information, see [Consumption dashboard](../admin/performance/dashboard-analysis.md#consumption-dashboard).

#### Nodes

Expand Down
6 changes: 3 additions & 3 deletions docs/home/whats-new-2-16.md
Original file line number Diff line number Diff line change
Expand Up @@ -33,7 +33,7 @@ date: 2023-Dec-4

### Run:ai Administrator

* <!-- DONE RUN-13296/RUN-13299 TW - Administrator Messages - Doc gap, there is no page for settings.-->Added the capability for administrators to configure messages to users when they log into the platform. Messages are configured using the *Message Editor* screen. For more information, see [Administrator Messages](../admin/admin-ui-setup/overview.md#administrator-messages).
* <!-- DONE RUN-13296/RUN-13299 TW - Administrator Messages - Doc gap, there is no page for settings.-->Added the capability for administrators to configure messages to users when they log into the platform. Messages are configured using the *Message Editor* screen. For more information, see [Administrator Messages](../admin/runai-setup/config/admin-messages.md).

#### Monitoring and Analytics

Expand All @@ -42,15 +42,15 @@ date: 2023-Dec-4
* Added a chart displaying the number of free GPUs per node. Free GPU are GPUs that have not been allocated to a workload.
* Added a dashlet that displays the total vs. ready resources for GPUs and CPUs. The dashlet indicates how many total nodes are in the platform, and how many are available.

For more information, see [Total and Ready GPU or CPU Nodes](../admin/admin-ui-setup/dashboard-analysis.md#total-and-ready-gpu-or-cpu-nodes).
For more information, see [Total and Ready GPU or CPU Nodes](../admin/performance/dashboard-analysis.md#total-and-ready-gpu-or-cpu-nodes).

* <!-- DONE RUN-14703 - Additional columns to consumption report -->Added additional columns to the consumption report for both *Projects* and *Departments* tables. The new columns are:

* GPU Idle allocated hours&mdash;the portion of time the GPUs spend idle from the total allocation hours.
* CPU usage hours&mdash;the actual usage time of CPU.
* Memory usage time&mdash;the actual usage time of CPU memory.

For more information, see [Consumption Dashboard](../admin/admin-ui-setup/dashboard-analysis.md#consumption-dashboard).
For more information, see [Consumption Dashboard](../admin/performance/dashboard-analysis.md#consumption-dashboard).

#### Authentication and Authorization

Expand Down
Loading
Loading