Skip to content

Commit 459d17e

Browse files
Merge pull request #757 from jasonnovichRunAI/RUN-15680-Demo-Runai-integration-with-OpenShift-AI
RUN-15680-Demo-Runai-integration-with-OpenShift-AI
2 parents 325e44e + 6f71440 commit 459d17e

File tree

1 file changed

+48
-1
lines changed

1 file changed

+48
-1
lines changed

docs/admin/admin-ui-setup/project-setup.md

Lines changed: 48 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -100,14 +100,14 @@ To view a project policy:
100100
* Default
101101
* Source
102102

103-
104103
## Other Project Properties
105104

106105
### Download Project Table
107106

108107
You can download the Projects table to a CSV file. Downloading a CSV can provide a snapshot history of your projects over the course of time, and help with compliance tracking. All the columns that are selected (displayed) in the table will be downloaded to the file.
109108

110109
To download the Projects table to a CSV:
110+
111111
1. Open *Projects*.
112112
2. From the *Columns* icon, select the columns you would like to have displayed in the table.
113113
3. Click on the ellipsis labeled *More*, and download the CSV.
@@ -229,6 +229,53 @@ To set a duration limit for Training Jobs:
229229

230230
The setting only takes effect for Jobs that have started after the duration has been changed.
231231

232+
## Setting Run:ai as default scheduler per Project/Namespace
233+
234+
By default, Kubernetes will use its native scheduler to schedule any type of submitted workload. However, Kubernetes also provides a standard way to use other schedulers such as Run:ai. This is done by adding to the submitted container workload’s YAML file:
235+
236+
`schedulerName: runai-scheduler`
237+
238+
There may be cases where you cannot change the YAML file and still want to use the Run:ai Scheduler to schedule those workloads. For these cases, another option is to configure the Run:ai Scheduler as the default scheduler for a specific namespace (Project). This will now make any workload type that is submitted to that namespace (Project) use the Run:ai scheduler. To configure this, add the following annotation on the namespace itself:
239+
240+
`runai/enforce-scheduler-name: true`
241+
242+
### Example
243+
244+
To annotate a project named `proj-a`, use the following command:
245+
246+
```bash
247+
kubectl annotate ns runai-proj-a runai/enforce-scheduler-name=true
248+
```
249+
250+
Verify the namespace in yaml format to see the annotation:
251+
252+
```bash
253+
kubectl get ns runai-proj-a -o yaml
254+
```
255+
256+
Output:
257+
258+
```YAML
259+
apiVersion: v1
260+
kind: Namespace
261+
metadata:
262+
annotations:
263+
runai/enforce-scheduler-name: "true"
264+
creationTimestamp: "2024-04-09T08:15:50Z"
265+
labels:
266+
kubernetes.io/metadata.name: runai-proj-a
267+
runai/namespace-version: v2
268+
runai/queue: proj-a
269+
name: runai-proj-a
270+
resourceVersion: "388336"
271+
uid: c53af666-7989-43df-9804-42bf8965ce83
272+
spec:
273+
finalizers:
274+
- kubernetes
275+
status:
276+
phase: Active
277+
```
278+
232279
## See Also
233280
234281
Run:ai supports an additional (optional) level of resource allocation called [Departments](department-setup.md).

0 commit comments

Comments
 (0)