Chapter 3. Managing cluster resources

Procedure

1. To enable GPU support on an OpenShift cluster, follow the instructions here: NVIDIA GPU Operator on Red Hat OpenShift Container Platform in the NVIDIA documentation.

2. Delete the migration-gpu-status ConfigMap.

   1. In the OpenShift Container Platform web console, switch to the Administrator perspective.
   2. Set the Project to All Projects or redhat-ods-applications to ensure you can see the appropriate ConfigMap.
   3. Search for the migration-gpu-status ConfigMap.

   4. Click the action menu (⋮) and select Delete ConfigMap from the list.

      The Delete ConfigMap dialog appears.

   5. Inspect the dialog and confirm that you are deleting the correct ConfigMap.
   6. Click Delete.

3. Restart the dashboard replicaset.

   1. In the OpenShift Container Platform web console, switch to the Administrator perspective.
   2. Click Workloads Deployments.
   3. Set the Project to All Projects or redhat-ods-applications to ensure you can see the appropriate deployment.
   4. Search for the rhods-dashboard deployment.
   5. Click the action menu (⋮) and select Restart Rollout from the list.
   6. Wait until the Status column indicates that all pods in the rollout have fully restarted.

Procedure

1. To enable Habana Gaudi devices in OpenShift AI, follow the instructions at HabanaAI Operator for OpenShift.

2. From the OpenShift AI dashboard, click Settings Accelerator profiles.

   The Accelerator profiles page appears, displaying existing accelerator profiles. To enable or disable an existing accelerator profile, on the row containing the relevant accelerator profile, click the toggle in the Enable column.

3. Click Create accelerator profile.

   The Create accelerator profile dialog opens.

4. In the Name field, enter a name for the Habana Gaudi device.
5. In the Identifier field, enter a unique string that identifies the Habana Gaudi device, for example, habana.ai/gaudi.
6. Optional: In the Description field, enter a description for the Habana Gaudi device.
7. To enable or disable the accelerator profile for the Habana Gaudi device immediately after creation, click the toggle in the Enable column.

8. Optional: Add a toleration to schedule pods with matching taints.

   1. Click Add toleration.

      The Add toleration dialog opens.

   2. From the Operator list, select one of the following options:

      • Equal - The key/value/effect parameters must match. This is the default.
      • Exists - The key/effect parameters must match. You must leave a blank value parameter, which matches any.

   3. From the Effect list, select one of the following options:

      • None
      • NoSchedule - New pods that do not match the taint are not scheduled onto that node. Existing pods on the node remain.
      • PreferNoSchedule - New pods that do not match the taint might be scheduled onto that node, but the scheduler tries not to. Existing pods on the node remain.
      • NoExecute - New pods that do not match the taint cannot be scheduled onto that node. Existing pods on the node that do not have a matching toleration are removed.
   4. In the Key field, enter the toleration key habana.ai/gaudi. The key is any string, up to 253 characters. The key must begin with a letter or number, and may contain letters, numbers, hyphens, dots, and underscores.
   5. In the Value field, enter a toleration value. The value is any string, up to 63 characters. The value must begin with a letter or number, and may contain letters, numbers, hyphens, dots, and underscores.

   6. In the Toleration Seconds section, select one of the following options to specify how long a pod stays bound to a node that has a node condition.

      • Forever - Pods stays permanently bound to a node.
      • Custom value - Enter a value, in seconds, to define how long pods stay bound to a node that has a node condition.
   7. Click Add.
9. Click Create accelerator profile.