V2.14 (#463)

jasonnovichRunAI · yarongol · web-flow · commit 7d2f90b4c6fa · 2023-09-03T11:10:22.000+03:00
* get-jobs-example

* default-storage-class-sample

* default-storage-class-sample

* sso-changes

* researcher-auth-for-sso

* [RUN-11536] update whats new with version content

* [RUN-11536] add RUN-10575 description.

* moved try azure to graveyard

* update TOC remove azure

* [RUN-11536] whats new update up to staging

---------

Co-authored-by: Yaron &lt;yaron@run.ai&gt;
diff --git a/docs/Researcher/user-interface/workspaces/create/workspace-v2.md b/docs/Researcher/user-interface/workspaces/create/workspace-v2.md
@@ -16,19 +16,25 @@ To create a new workspace:
 
 4. Enter a name for your workspace and press *Continue*.
 5. Select an environment from the tiles. If your environment is not listed, use the *Search environments* box to find it. Press *New environment* to create an environment if needed.
-   1. Press *Commands and Arguments* to add special commands and arguments to your environment selection.
-   2. Press *Environment variable* to add an environment variable. Press again if you need more environments variables.
+
+      1. Press *Commands and Arguments* to add special commands and arguments to your environment selection.
+      2. Press *Environment variable* to add an environment variable. Press again if you need more environments variables.
+
 6. Select a compute resource from the tiles. If your compute resource is not listed, use the *Search compute resources* box to find it. Press *New compute resource* to create a compute resource if needed.
 7. Open the *Volume* pane, and press *Volume* to add a volume to your workspace.
-   1. Select the *Storage class* from the dropdown.
-   2. Select the *Access mode* from the dropdown.
-   3. Enter a claim size, and select the units.
-   4. Select a *Volume system*, mode from the dropdown.
-   5. Enter the *Container path* for volume target location.
-   6. Select a *Volume persistency.
+
+      1. Select the *Storage class* from the dropdown.
+      2. Select the *Access mode* from the dropdown.
+      3. Enter a claim size, and select the units.
+      4. Select a *Volume system*, mode from the dropdown.
+      5. Enter the *Container path* for volume target location.
+      6. Select a *Volume persistency*. Choose from *Persistent* or *Ephemeral*.
+
 8. Select a data source from the tiles. If your data source is not listed, use the *Search compute resources* box to find it. Press *New data source* to create a new data source if needed.
 9. In the *General* pane, add special settings for your workspace:
-   1. Press *Auto-deletion* to delete the workspace automatically when it either completes or fails. You can configure the timeframe in days, hours, minuets, and seconds. If the timeframe is set to 0, the workspace will be deleted immediately after it completes or fails.
-   2. Press *Annotation* to a name and value to annotate the workspace. Repeat this step to add multiple annotations.
-   3. Press *Label* to a name and value to label the workspace. Repeat this step to add multiple labels.
+
+      1. Press *Auto-deletion* to delete the workspace automatically when it either completes or fails. You can configure the timeframe in days, hours, minuets, and seconds. If the timeframe is set to 0, the workspace will be deleted immediately after it completes or fails.
+      2. Press *Annotation* to a name and value to annotate the workspace. Repeat this step to add multiple annotations.
+      3. Press *Label* to a name and value to label the workspace. Repeat this step to add multiple labels.
+
 10. Press *Create workspace*
diff --git a/docs/admin/admin-ui-setup/dashboard-analysis.md b/docs/admin/admin-ui-setup/dashboard-analysis.md
@@ -257,7 +257,7 @@ Provides a holistic, aggregated view across Clusters, including information abou
 
 ## Consumption dashboard
 
-This dashboard enables users and admins to view consumption usage using run:AI services. The dashboard provides views based on configurable filters and timelines.
+This dashboard enables users and admins to view consumption usage using run:AI services. The dashboard provides views based on configurable filters and timelines. The dashboard also provides costing analysis for GPU, CPU, and memory costs for the system.
 
 ![!copnsumption dasboard](img/consumption-dashboard.png)
 
diff --git a/docs/admin/workloads/policies.md b/docs/admin/workloads/policies.md
@@ -66,6 +66,8 @@ gpu: must be no greater than 4
 
 A similar message will appear in the _New Job_ form of the Run:ai user interface, when attempting to enter the number of GPUs, which is out of range for a training job.
 
+#### GPU and CPU memory limits
+
 The following policy places a default and limit on the available values for CPU and GPU memory allocation.
 
 ```YAML title="gpumemorypolicy.yaml"
diff --git a/docs/home/whats-new-2-14.md b/docs/home/whats-new-2-14.md
@@ -13,43 +13,46 @@ This version contains features and fixes from previous versions starting with 2.
 * [What's new 2.13](whats-new-2-13.md)
 * [What's new 2.12](whats-new-2-12.md)
 * [What's new 2.10](whats-new-2-10.md)
-<!-- TODO RBAC RUN-7510/9002 and lots of others -->
+<!-- RUN-7510/9002 and lots of others -->
 
 ##### Role based access control
 
 Stating in this version, Run:ai had updated the authorization system to Role Based Access Control (RBAC). RBAC is a policy-neutral access control mechanism defined around roles and privileges. For more information, see [Role based access control](../admin/runai-setup/access-control/rbac.md#role-based-access-control).
 
-When upgrading the system, previous access and authorizations that were configured will be migrated to the new RBAC roles. See the table below for role conversions:
+<!-- When upgrading the system, previous access and authorizations that were configured will be migrated to the new RBAC roles. See the table below for role conversions:
 
-| Previous user type | RBAC role |
-| -- | -- |
-| Admin | [System admin](../admin/runai-setup/access-control/rbac.md#roles) |
-| next one | [next one](../admin/runai-setup/access-control/rbac.md#roles) |
+TODO Add RBAC old--new conversion table here. -->
 
+##### Auto delete jobs
 <!-- RUN-8586/RUN-11777 -->
-<!-- TODO add RUN-11777 docs to here and to the correct page as there are more config options -->
+* We are pleased to announce new functionality in our UI and CLI that provides configuration options which automatically delete jobs after a specified amount of time. Auto-deletion provides more efficient use of resources and makes it easier for researchers to manage their jobs. For more configuration options in the UI, see Auto deletion (Step 9) in [Create a new workspace](../Researcher/user-interface/workspaces/create/.workspace-v2.md#create-a-new-workspace). For more information on the CLI flag, see [--auto-deletion-time-after-completion](../Researcher/cli-reference/runai-submit.md#auto-deletion-time-after-completion).
 
+##### Multiple service types
 <!-- RUN-10235/RUN-10485  Support multi service types in the CLI submission -->
-* We are pleased to announce new functionality in our CLI that allows the submitting a workload with multiple service types at the same time in a CSV style format. Both the CLI and the UI now provide the same functionality.
+* We are pleased to announce new functionality in our CLI that allows submitting a workload with multiple service types at the same time in a CSV style format. Both the CLI and the UI now provide the same functionality. For more information see [runai submit ](../Researcher/cli-reference/runai-submit.md#s----service-type-string).
 
-<!-- RUN-9808/RUN-9810 Show effective project policy from the UI -->
-* We are pleased to announce an enhancement to the Projects table where users now have the ability to view policies from within a project. For more information, see [Projects]().
+<!-- RUN-9808/RUN-9810 Show effective project policy from the UI 
+* We are pleased to announce an enhancement to the Projects table where users now have the ability to view policies from within a project. For more information, see [Projects](). -->
 
+##### Ephemeral volumes
 <!--RUN-9958/RUN-10061 Ephemeral volumes in workspaces -->
+* We are pleased to announce support for Ephemeral volumes in *Workspaces*. Ephemeral storage is tied to the lifecycle of the *Workspace*. It’s temporary storage that gets wiped out and lost when the workspace is deleted. Ephemeral storage is added to the *Workspace* configuration form in the *Volume* pane. For configuration information, see step 7 in [Create a new workspace](../Researcher/user-interface/workspaces/create/.workspace-v2.md#create-a-new-workspace).
 
+##### Email notifications
 <!-- RUN-9868/RUN-10087 support per user scheduling events notifications (slack/email) -->
-* We are pleased to announce new functionality where users can now receive notifications from scheduling events. Researchers using Run:ai can now receive notifications via email and is configured so that each user will only get the events relevant to their workloads. For more information, see [email notifications]().
+* We are pleased to announce new functionality where users can now receive notifications from scheduling events. Researchers using Run:ai can now receive notifications via email and is configured so that each user will only get the events relevant to their workloads. For more information, see [email notifications](../admin/researcher-setup/email-messaging.md#email-notifications).
 
+##### CLI improvements
 <!-- RUN-10335/RUN-10510 Node port command line -->
+* We are pleased to announce improved functionality in the `runai submit` command which now clarifies the port for the container using the `nodeport` flag. For more information, see `runai submit`, [--service-type](../Researcher/cli-reference/runai-submit.md#s----service-type-string) `nodeport`.
 
+##### Policy improvements
 <!-- RUN-10575/RUN-10579 Add numeric rules in the policy to GPU memory, CPU memory & CPU -->
-* We are pleased to announce that we have increased the flexibility when creating policies. The improved flexibility includes the abililty to allocate a `min` and a `max` value for CPU and GPU memory.
+* We are pleased to announce increased flexibility when creating policies. The improved flexibility includes the abililty to allocate a `min` and a `max` value for CPU and GPU memory. For configuration information, see [GPU and CPU memory limits](../admin/workloads/policies.md#gpu-and-cpu-memory-limits) in *Configuring policies*.
 
+##### Resource costing
 <!-- RUN-11421/RUN-11508 Consumption report cost and bugs -->
-* We are pleased to announce that we have added an additional table to the Consumption dashboard. This table contains the consumption per department and the cost per department. For more information, see [Consumption dashboard]()
-
-<!-- RUN-8586/RUN-11777 Auto delete completed/failed jobs -->
-
+* We are pleased to announce that we have added an additional table to the Consumption dashboard. This table contains the consumption per department and the cost per department. For more information, see [Consumption dashboard](../admin/admin-ui-setup/dashboard-analysis.md#consumption-dashboard).
 
 #### Fixed issues
 
