Skip to content

Commit 9250416

Browse files
Merge pull request #487 from jasonnovichRunAI:v2.14
whats new changes
2 parents 5d31f15 + 9cbd0fe commit 9250416

File tree

1 file changed

+12
-14
lines changed

1 file changed

+12
-14
lines changed

docs/home/whats-new-2-14.md

Lines changed: 12 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -1,49 +1,47 @@
1-
# Run:ai version 2.14
1+
# Run:ai version 2.14 - September, 18, 2023
22

3-
## Version 2.14.0 September, 18, 2023
3+
## Release content
44

5-
### Release content
6-
7-
#### Role based access control
5+
### Role based access control
86
<!-- RUN-7510/9002 and lots of others -->
97
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).
108

119
<!-- 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:
1210
1311
TODO Add RBAC old--new conversion table here. -->
1412

15-
#### Auto delete jobs
13+
### Auto delete jobs
1614
<!-- RUN-8586/RUN-11777 -->
1715
* 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).
1816

19-
#### Multiple service types
17+
### Multiple service types
2018
<!-- RUN-10235/RUN-10485 Support multi service types in the CLI submission -->
2119
* 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).
2220

2321
<!-- RUN-9808/RUN-9810 Show effective project policy from the UI
2422
* 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](). -->
2523

26-
#### Ephemeral volumes
24+
### Ephemeral volumes
2725
<!--RUN-9958/RUN-10061 Ephemeral volumes in workspaces -->
2826
* 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).
2927

30-
#### Email notifications
28+
### Email notifications
3129
<!-- RUN-9868/RUN-10087 support per user scheduling events notifications (slack/email) -->
3230
* 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).
3331

34-
#### CLI improvements
32+
### CLI improvements
3533
<!-- RUN-10335/RUN-10510 Node port command line -->
3634
* 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`.
3735

38-
#### Policy improvements
36+
### Policy improvements
3937
<!-- RUN-10575/RUN-10579 Add numeric rules in the policy to GPU memory, CPU memory & CPU -->
4038
* We are pleased to announce increased flexibility when creating policies. The improved flexibility includes the ability 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*.
4139

42-
#### Resource costing
40+
### Resource costing
4341
<!-- RUN-11421/RUN-11508 Consumption report cost and bugs -->
4442
* 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).
4543

46-
#### Deployment improvements
44+
### Deployment improvements
4745
<!-- RUN-11563/RUN-11564 MPS and tolerance -->
4846
* We are pleased to announce improvements to the deployment form which now include support for and *Multi-Process Service (MPS)*. *MPS* is a service which allows the running of parallel processes on the same GPU, which are all run by the same userid. To enable *MPS* support, move the selector switch on the *Deployments* form.
4947

@@ -64,7 +62,7 @@ To configure *Tolerations*:
6462
4. Enter a *Value* and *Toleration seconds* (optional).
6563
4. When your form is complete press *Deploy*.
6664

67-
#### Fixed issues
65+
### Fixed issues
6866

6967
| Internal ID | Description |
7068
| ---------------------------- | ---- |

0 commit comments

Comments
 (0)