Departments

This article explains the procedure for managing departments

Departments are a grouping of projects. By grouping projects into a department, you can set quota limitations to a set of projects, create policies that are applied to the department, and create assets that can be scoped to the whole department or a partial group of descendent projects

For example, in an academic environment, a department can be the Physics Department grouping various projects (AI Initiatives) within the department, or grouping projects where each project represents a single student.

Departments¶

The Departments table can be found under Departments in the Run:ai platform.

The Departments table lists all departments defined for a specific cluster and allows you to manage them. You can switch between clusters by selecting your cluster using the filter at the top.

The Departments table consists of the following columns:

Customizing the table view¶

• Filter - Click ADD FILTER, select the column to filter by, and enter the filter values
• Search - Click SEARCH and type the value to search by
• Sort - Click each column header to sort by
• Column selection - Click COLUMNS and select the columns to display in the table
• Download table - Click MORE and then Click Download as CSV

Node pools with quota associated with the department¶

Click one of the values of Node pool(s) with quota column, to view the list of node pools and their parameters

Subjects authorized for the project¶

Click one of the values of the Subject(s) column, to view the list of subjects and their parameters. This column is only viewable if your role in the Run:ai system affords you those permissions.

Adding a new department¶

To create a new Department:

1. Click +NEW DEPARTMENT
2. Select a scope.
   By default, the field contains the scope of the current UI context cluster, viewable at the top left side of your screen. You can change the current UI context cluster by clicking the ‘Cluster: cluster-name’ field and applying another cluster as the UI context. Alternatively, you can choose another cluster within the ‘+ New Department’ form by clicking the organizational tree icon on the right side of the scope field, opening the organizational tree and selecting one of the available clusters.
3. Enter a name for the department. Department names must start with a letter and can only contain lower case latin letters, numbers or a hyphen ('-’).
4. Under Quota Management, select a quota for the department. The Quota management section may contain different fields depending on pre-created system configuration. Possible system configurations are:
   • Existence of Node Pools
   • CPU Quota - Allow setting a quota for CPU resources.

When no node pools are configured, you can set the following quota parameters:

• GPU Devices
  The number of GPUs you want to allocate for this department (decimal number). This quota is consumed by the department’s subordinated project.
• CPUs (cores) (when CPU quota is set)
  The number of CPU cores you want to allocate for this department (decimal number). This quota is consumed by the department’s subordinated projects
• CPUs memory (when CPU quota is set)
  The amount of CPU memory you want to allocate for this department (in Megabytes or Gigabytes). This quota is consumed by the department’s subordinated projects

When node pools are enabled, it is possible to set the above quota parameters for each node-pool separately.

• Order of priority This column is displayed only if more than one node pool exists. The default order in which the Scheduler uses node pools to schedule a workload. This means, the Scheduler first tries to allocate resources using the highest priority node pool, followed by the next in priority, until it reaches the lowest priority node pool list, then the Scheduler starts from the highest priority again. The Scheduler uses the department list of prioritized node pools, only if the order of priority of node pools is not set in project or the workload during submission (either by an admin policy or by the user). An empty value indicates that the node pool is not part of the department’s default node pool priority list, but a node pool can still be chosen by the admin policy or a user during workload submission. Department nodepool priority sets defaults to the subordinate projects but does not enforce it, meaning projects are free to change their priority.
• In addition, you can decide whether to allow a department to go over-quota. Allowing over-quota at the department level means that one department can receive more resources than its quota when not required by other departments. If the over-quota is disabled, workloads running under subordinated projects are not able to use more resources than the department’s quota, but each project can still go over-quota (if enabled at the project level) up to the department’s quota.

Unlimited CPU(Cores) and CPU memory quotas are an exception - in this case, workloads of subordinated projects can consume available resources up to the physical limitation of the cluster or any of the node pools.

Example of Quota management:

1. Click CREATE DEPARTMENT

Adding an access rule to a department¶

To create a new access rule for a department:

1. Select the department you want to add an access rule for
2. Click ACCESS RULES
3. Click +ACCESS RULE
4. Select a subject
5. Select or enter the subject identifier:
   • User Email for a local user created in Run:ai or for SSO user as recognized by the IDP
   • Group name as recognized by the IDP
   • Application name as created in Run:ai
6. Select a role
7. Click SAVE RULE
8. Click CLOSE

Deleting an access rule from a department¶

To delete an access rule from a department:

1. Select the department you want to remove an access rule from
2. Click ACCESS RULES
3. Find the access rule you would like to delete
4. Click on the trash icon
5. Click CLOSE

Editing a department¶

1. Select the Department you want to edit
2. Click EDIT
3. Update the Department and click SAVE

Viewing a department’s policy¶

To view the policy of a department:

1. Select the department for which you want to view its policies.
   This option is only active if the department has defined policies in place.
2. Click VIEW POLICY and select the workload type for which you want to view the policies:
   a. Workspace workload type policy with its set of rules
   b. Training workload type policies with its set of rules
3. In the Policy form, view the workload rules that are enforcing your department for the selected workload type as well as the defaults:
   • Parameter - The workload submission parameter that Rule and Default is applied on
   • Type (applicable for data sources only) - The data source type (Git, S3, nfs, pvc etc.)
   • Default - The default value of the Parameter
   • Rule - Set up constraints on workload policy fields
   • Source - The origin of the applied policy (cluster, department or project)

Deleting a department¶

1. Select the department you want to delete
2. Click DELETE
3. On the dialog, click DELETE to confirm the deletion

Reviewing a department¶

1. Select the department you want to review
2. Click REVIEW
3. Review and click CLOSE

Using API¶

Go to the Departments API reference to view the available actions