Ironic supports pluggable back-end drivers for different types of hardware to enable features specific to unique hardware platforms and leverage divergent capabilities via a common API . This API is divided into three sections: core, common, and vendor. While authors of vendor drivers may break new ground in the designated "vendor_passthru" section of the API, they are strongly encouraged to converge on a common API across vendors. More details may be found under the system architecture description.
Hardware drivers must undergo CI testing so as to ensure their continued functionality. Some drivers will be tested upstream, while many will require third-party CI testing due to the unique nature of their hardware (and the unmanageable complexity were a single team required to maintain a test infrastructure encompassing hardware from many diverse vendors). Guidelines on that testing can be found on the Ironic/Testing wiki page.
Out-of-tree drivers are supported by Ironic and may be loaded via python entrypoints.
The table below describes the CI test coverage of the drivers present in Ironic's tree upstream.
Note that drivers are composed of more than one interface (eg, power and deploy). Not all combinations of interfaces are necessarily tested, but we are striving to get test coverage for each interface in at least one driver.
|Interface Type||Interface Name||Test coverage provided by driver name|
|deploy||agent||Used in production for Rackspace OnMetal, lacks upstream CI|
|power||ipminative||pxe_ipminative (provided by ibm-xcat-ci)|
|power||ipmitool||** most widely used power driver in production, but lacks upstream CI|
|Driver Name||Primary Contact Email and IRC handle||Testing Status|
|pxe_ssh||devananda (devananda dot vdv at gmail)||tested in the upstream gate|
|pxe_ipminative||linggao (linggao at us dot ibm dot com)||Third-party CI: "ibm-xcat-ci" <firstname.lastname@example.org>|
|pxe_ipmitool||devananda (devananda dot vdv at gmail)||used by TripleO, but not CI tested|