Red Hat Summit Red Hat SummitSupportConsoleDéveloppeursCommencer un essaiContact

Ce contenu n'est pas disponible dans la langue sélectionnée.

Chapter 7. Working with accelerator profiles

Important

Accelerator profiles are now deprecated. To target specific worker nodes for workbenches or model serving workloads, use hardware profiles. By default, the accelerator profiles feature is still displayed in the dashboard navigation menu, while the hardware profiles feature is hidden.

To disable accelerator profiles in the dashboard navigation menu, set the disableAcceleratorProfiles value to true in the OdhDashboardConfig Custom Resource (CR) in OpenShift. To enable hardware profiles, set the disableHardwareProfiles value to false in the same CR.

Note: The spec.dashboardConfig.disableAcceleratorProfiles option is superseded by the spec.dashboardConfig.disableHardwareProfiles option. If both options are set to false, the disableHardwareProfiles option overrides the disableAcceleratorProfiles option, and the Settings Hardware profiles menu item is shown in the dashboard navigation menu.

For more information about setting dashboard configuration options, see Customizing the dashboard.

Red Hat recommends that you migrate any existing accelerator profiles to hardware profiles as soon as possible to ensure continued support and compatibility.

To configure accelerators for your data scientists to use in OpenShift AI, you must create an associated accelerator profile. An accelerator profile is a custom resource definition (CRD) on OpenShift that has an AcceleratorProfile resource, and defines the specification of the accelerator. You can create and manage accelerator profiles by selecting Settings Accelerator profiles on the OpenShift AI dashboard.

For accelerators that are new to your deployment, you must manually configure an accelerator profile for each accelerator. If your deployment contains an accelerator before you upgrade, the associated accelerator profile remains after the upgrade. You can manage the accelerators that appear to your data scientists by assigning specific accelerator profiles to your custom workbench images. This example shows the code for a Habana Gaudi 1 accelerator profile: 

---
apiVersion: dashboard.opendatahub.io/v1alpha
kind: AcceleratorProfile
metadata:
  name: hpu-profile-first-gen-gaudi
spec:
  displayName: Habana HPU - 1st Gen Gaudi
  description: First Generation Habana Gaudi device
  enabled: true
  identifier: habana.ai/gaudi
  tolerations:
    - effect: NoSchedule
      key: habana.ai/gaudi
      operator: Exists
---
Copy to Clipboard Toggle word wrap

The accelerator profile code is displayed on the Instances tab on the details page for the AcceleratorProfile custom resource definition (CRD). For more information about accelerator profile attributes, see the following table:

Expand
Table 7.1. Accelerator profile attributes
AttributeTypeRequiredDescription

displayName

String

Required

The display name of the accelerator profile.

description

String

Optional

Descriptive text defining the accelerator profile.

identifier

String

Required

A unique identifier defining the accelerator resource.

enabled

Boolean

Required

Determines if the accelerator is visible in OpenShift AI.

tolerations

Array

Optional

The tolerations that can apply to workbenches and serving runtimes that use the accelerator. For more information about toleration attributes in OpenShift AI, see Toleration v1 core.

7.1. Viewing accelerator profiles
Copier lien

If you have defined accelerator profiles for OpenShift AI, you can view, enable, and disable them from the Accelerator profiles page.

Prerequisites

  • You have logged in to OpenShift AI as a user with OpenShift AI administrator privileges.
  • Your deployment contains existing accelerator profiles.

Procedure

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

    The Accelerator profiles page opens, displaying existing accelerator profiles.

  2. Inspect the list of accelerator profiles. To enable or disable an accelerator profile, on the row containing the accelerator profile, click the toggle in the Enable column.

Verification

  • The Accelerator profiles page opens, displaying existing accelerator profiles.

7.2. Creating an accelerator profile
Copier lien

To configure accelerators for your data scientists to use in OpenShift AI, you must create an associated accelerator profile.

Prerequisites

  • You have logged in to OpenShift AI as a user with OpenShift AI administrator privileges.

Procedure

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

    The Accelerator profiles page opens, 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.

  2. Click Create accelerator profile.

    The Create accelerator profile dialog opens.

  3. In the Name field, enter a name for the accelerator profile.
  4. In the Identifier field, enter a unique string that identifies the hardware accelerator associated with the accelerator profile.
  5. Optional: In the Description field, enter a description for the accelerator profile.
  6. To enable or disable the accelerator profile immediately after creation, click the toggle in the Enable column.

  7. 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 a toleration key. 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.
  8. Click Create accelerator profile.

Verification

  • The accelerator profile is displayed on the Accelerator profiles page.
  • The Accelerator list is displayed on the Start a basic workbench page. After you select an accelerator, the Number of accelerators field is displayed, which you can use to choose the number of accelerators for your workbench.
  • The accelerator profile is displayed on the Instances tab on the details page for the AcceleratorProfile custom resource definition (CRD).

7.3. Updating an accelerator profile
Copier lien

You can update the existing accelerator profiles in your deployment. You might want to change important identifying information, such as the display name, the identifier, or the description.

Prerequisites

  • You have logged in to OpenShift AI as a user with OpenShift AI administrator privileges.
  • The accelerator profile exists in your deployment.

Procedure

  1. From the OpenShift AI dashboard, click Settings Workbench images.

    The Workbench images page opens. Previously imported workbench images are displayed. To enable or disable a previously imported workbench image, on the row containing the relevant workbench image, click the toggle in the Enable column.

  2. Click the action menu (⋮) and select Edit from the list.

    The Edit accelerator profile dialog opens.

  3. In the Name field, update the accelerator profile name.
  4. In the Identifier field, update the unique string that identifies the hardware accelerator associated with the accelerator profile, if applicable.
  5. Optional: In the Description field, update the accelerator profile.
  6. To enable or disable the accelerator profile immediately after creation, click the toggle in the Enable column.

  7. 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 a toleration key. 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.

  8. If your accelerator profile contains existing tolerations, you can edit them.

    1. Click the action menu (⋮) on the row containing the toleration that you want to edit and select Edit from the list.
    2. Complete the applicable fields to update the details of the toleration.
    3. Click Update.
  9. Click Update accelerator profile.

Verification

  • If your accelerator profile has new identifying information, this information is displayed in the Accelerator list on the Start a basic workbench page.

7.4. Deleting an accelerator profile
Copier lien

To discard accelerator profiles that you no longer require, you can delete them so that they do not appear on the dashboard.

Prerequisites

  • You have logged in to OpenShift AI as a user with OpenShift AI administrator privileges.
  • The accelerator profile that you want to delete exists in your deployment.

Procedure

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

    The Accelerator profiles page opens, displaying existing accelerator profiles.

  2. Click the action menu (⋮) beside the accelerator profile that you want to delete and click Delete.

    The Delete accelerator profile dialog opens.

  3. Enter the name of the accelerator profile in the text field to confirm that you intend to delete it.
  4. Click Delete.

Verification

  • The accelerator profile is no longer displayed on the Accelerator profiles page.
Retour au début
Red Hat logoGithubredditYoutubeTwitter

Apprendre

Essayez, achetez et vendez

Communautés

À propos de la documentation Red Hat

Nous aidons les utilisateurs de Red Hat à innover et à atteindre leurs objectifs grâce à nos produits et services avec un contenu auquel ils peuvent faire confiance. Découvrez nos récentes mises à jour.

Rendre l’open source plus inclusif

Red Hat s'engage à remplacer le langage problématique dans notre code, notre documentation et nos propriétés Web. Pour plus de détails, consultez le Blog Red Hat.

À propos de Red Hat

Nous proposons des solutions renforcées qui facilitent le travail des entreprises sur plusieurs plates-formes et environnements, du centre de données central à la périphérie du réseau.

Theme

© 2025 Red Hat