OPCP Core compatibility matrix

View as Markdown

Find out which OS images and platforms are validated for OPCP Core bare metal provisioning — Ironic features, hardware qualification, and available documentation

Objective

OPCP Core provides bare metal provisioning through OpenStack Ironic. Because this requires specific hardware support and validated firmware versions, not every OS image works out of the box — and firmware updates can break compatibility.

This guide is a public compatibility matrix listing platforms that have been fully qualified on OPCP Core. For each, it documents:

  • Whether the platform is available upon delivery (provisioned directly by OVHcloud without a custom image).
  • Which Ironic features are supported: software RAID, Active/Backup bonding, LACP (802.3ad).
  • Whether Neutron trunking is available post-install.
  • Whether Secure Boot is supported.
  • Links to the relevant image build and installation documentation.

Compatibility matrix

The table below lists platforms with status Ready — those that have been fully qualified on OPCP Core hardware.

Info

The "Available upon delivery" column indicates whether OPCP Core can provision this OS on your bare metal nodes at delivery time, without requiring you to build a custom image first.

PlatformAvailable upon deliveryGeneric Bare Metal hardwareIronic software RAIDIronic Active/Backup bondingIronic LACP (802.3ad)Neutron trunkingSecure BootImage build guideInstallation guide
Debian 12YesYesNoYesYesYesYesGuideGuide
Debian 13YesYesNoYesYesYesYesGuideGuide

Feature explanations

Ironic software RAID

Software RAID is configured by Ironic during bare metal provisioning. When enabled, the OS is deployed across multiple disks (typically RAID-1 for two-disk configurations), providing local storage redundancy without requiring a hardware RAID controller.

Warning

Software RAID with Ironic requires GRUB to be built with mdadm modules. This must be taken into account when building a custom OS image.

Ironic Active/Backup bonding

Ironic can configure Active/Backup network bonding during provisioning. This provides link redundancy: one NIC is active while the other stands by, and takes over automatically if the primary fails. No configuration is required on the upstream switch.

Ironic LACP (802.3ad)

LACP bonding (IEEE 802.3ad) aggregates two network interfaces into a single logical link, providing both redundancy and increased throughput. This mode requires the upstream switch to support and be configured for LACP.

For step-by-step instructions, see How to setup LACP on a Node.

Neutron trunking

Neutron trunking allows a bare metal instance to carry multiple Neutron networks over a single physical port using VLAN tagging. It is configured post-installation through OpenStack Neutron, and not during the Ironic provisioning phase.

Info

OpenStack does not configure VLAN trunking natively through cloud-init. Enabling trunking requires post-install configuration steps detailed in How to setup trunk on a Node.

Secure Boot

UEFI Secure Boot ensures that only signed bootloaders and kernels are executed during the boot sequence. Support depends on both the OS image and the hardware configuration. A — in the matrix means this feature has not yet been validated for that platform.

Go further

For training or technical assistance implementing our solutions, contact your sales representative or visit our Professional Services page to request a quote and have your project analyzed by our experts.

Join our community of users.

Was this page helpful?