Upgrading to Hardware Types¶

Ironic Inspector¶

Some classic drivers, notably pxe_ipmitool, agent_ipmitool and pxe_drac_inspector, use ironic-inspector for their inspect interface.

The same functionality is available for all hardware types, but the appropriate inspect interface has to be enabled in the Bare Metal service configuration file, for example:

[DEFAULT]
enabled_inspect_interfaces = inspector,no-inspect

See Enabling drivers and hardware types for more details.

Then you can tell your nodes to use this interface, for example:

export OS_BAREMETAL_API_VERSION=1.31
for uuid in $(openstack baremetal node list --driver ipmi -f value -c UUID); do
    openstack baremetal node set $uuid --inspect-interface inspector
done

Console¶

Several classic drivers, notably pxe_ipmitool_socat and agent_ipmitool_socat, use socat-based serial console implementation.

For the ipmi hardware type it is used by default, if enabled in the configuration file:

[DEFAULT]
enabled_console_interfaces = ipmitool-socat,no-console

If you want to use the shellinabox implementation instead, it has to be enabled as well:

[DEFAULT]
enabled_console_interfaces = ipmitool-shellinabox,no-console

Then you need to update some or all nodes to use it explicitly. For example, to update all nodes use:

export OS_BAREMETAL_API_VERSION=1.31
for uuid in $(openstack baremetal node list --driver ipmi -f value -c UUID); do
    openstack baremetal node set $uuid --console-interface ipmitool-shellinabox
done

RAID¶

Many classic drivers, including pxe_ipmitool and agent_ipmitool use the IPA-based in-band RAID implementation by default.

For the hardware types it is not used by default. To use it, you need to enable it in the configuration first:

[DEFAULT]
enabled_raid_interfaces = agent,no-raid

Then you can update those nodes that support in-band RAID to use the agent RAID interface. For example, to update all nodes use:

export OS_BAREMETAL_API_VERSION=1.31
for uuid in $(openstack baremetal node list --driver ipmi -f value -c UUID); do
    openstack baremetal node set $uuid --raid-interface agent
done

Network and storage¶

The network and storage interfaces have always been dynamic, and thus do not require any special treatment during upgrade.

Vendor¶

Classic drivers are allowed to use the VendorMixin functionality to combine and expose several node or driver vendor passthru methods from different vendor interface implementations in one driver.

This is no longer possible with hardware types.

With hardware types, a vendor interface can only have a single active implementation from the list of vendor interfaces supported by a given hardware type.

Ironic no longer has in-tree drivers (both classic and hardware types) that rely on this VendorMixin functionality support. However if you are using an out-of-tree classic driver that depends on it, you’ll need to do the following in order to use vendor passthru methods from different vendor passthru implementations:

1. While creating a new hardware type to replace your classic driver, specify all vendor interface implementations your classic driver was using to build its VendorMixin as supported vendor interfaces (property supported_vendor_interfaces of the Python class that defines your hardware type).

2. Ensure all required vendor interfaces are enabled in the ironic configuration file under the [DEFAULT]enabled_vendor_interfaces option. You should also consider setting the [DEFAULT]default_vendor_interface option to specify the vendor interface for nodes that do not have one set explicitly.

3. Before invoking a specific vendor passthru method, make sure that the node’s vendor interface is set to the interface with the desired vendor passthru method. For example, if you want to invoke the vendor passthru method vendor_method_foo() from vendor_foo vendor interface:

   # set the vendor interface to 'vendor_foo`
   openstack --os-baremetal-api-version 1.31 baremetal node set <node> --vendor-interface vendor_foo
   
   # invoke the vendor passthru method
   openstack baremetal node passthru call <node> vendor_method_foo