Chapter 6. IBM Spyre integration


The IBM Spyre Operator integrates IBM Spyre accelerators directly into OpenShift AI workflows.

To enable IBM Spyre in OpenShift AI, you must perform the following tasks:

  • Install all necessary dependencies before you enable IBM Spyre accelerators in OpenShift AI.
  • Install the latest version of the IBM Spyre Operator from the software catalog.
  • After you install the IBM Spyre Operator, you must create an accelerator profile or hardware profile in OpenShift AI to expose IBM Spyre as an available accelerator resource for workloads.
Note

aiu-smi metrics collection tool in OpenShift on IBM Power

To run aiu-smi in an OpenShift environment on IBM Power, use the command oc exec <pod> -- aiu-smi, where <pod> is the pod starting with the model deployment name.

For more information on the aiu-smi tool, refer to the IBM Spyre for Power documentation on aiu-smi (except the View the command usage and output section).

For more detailed guidance on configuring IBM Spyre accelerators for production-ready deployments, contact IBM support.

6.1. Enabling IBM Spyre

Before you can use IBM Spyre AI accelerators in OpenShift AI, you must install the Spyre Operator.

Prerequisites

  • You have logged in to the OpenShift cluster.
  • You have the cluster-admin role in the OpenShift cluster.
  • Your worker nodes equipped with IBM Spyre accelerators meet the following hardware requirements:

    • A minimum of 512 GB of RAM.
    • A minimum of 500 GB of local disk space.
  • You have configured the IBM Spyre accelerators and verified that the cluster detects them.
  • You have applied the required MachineConfig objects as described in Specifying IBM Spyre MachineConfigs.

Procedure

  1. To enable IBM Spyre support on an OpenShift cluster, follow the instructions in IBM Spyre accelerator on Red Hat OpenShift Container Platform in the IBM documentation.
  2. After you install the Node Feature Discovery (NFD) Operator, create a NodeFeatureDiscovery instance.
  3. After you install the IBM Spyre Operator, create a SpyreClusterPolicy instance and populate it with default values.
  4. To use the default scheduler for IBM Spyre workloads, remove the externalDeviceReservation field from the SpyreClusterPolicy object under the spec.experimentalMode section.
  5. Create a hardware profile for the IBM Spyre accelerators. For more information, see Working with hardware profiles.

Verification

  1. Go to the Installed Operators page. The navigation path depends on your OpenShift version:

    • On OpenShift 4.20 and later, click Ecosystem Installed Operators.
    • On OpenShift 4.19, click Operators Installed Operators.
  2. Verify that the following operators appear with a status of Succeeded:

    • IBM Spyre Operator
    • Node Feature Discovery (NFD)
    • cert-manager Operator for Red Hat OpenShift
    • Secondary Scheduler Operator
  3. Verify that the cluster detects the IBM Spyre accelerators.

    Wait a few minutes after the installation completes, and then run the following command to describe a worker node:

    $ oc describe node <node_name>
  4. In the Capacity section of the output, verify that the ibm.com resources appear, similar to the following example:

    Capacity:
      cpu:                             16
      ephemeral-storage:               523823084Ki
      hugepages-1Gi:                   0
      hugepages-2Mi:                   0
      ibm.com/spyre_pf:                4
      ibm.com/spyre_pf_0481_50_00.0:   1
      ibm.com/spyre_pf_0482_60_00.0:   1
      ibm.com/spyre_pf_0483_70_00.0:   1
      ibm.com/spyre_pf_0484_80_00.0:   0
      ibm.com/spyre_pf_tier0:          3
      ibm.com/spyre_pf_tier1:          3
      ibm.com/spyre_pf_tier2:          3
      memory:                          1038738560Ki
      pods:                            250
Red Hat logoGithubredditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat Documentation

Legal Notice

Theme

© 2026 Red Hat
Back to top