A service for managing and provisioning Bare Metal servers.
0ad6f87587
This change adds idrac hardware type support of a virtual media boot interface implementation that utilizes the Redfish out-of-band (OOB) management protocol and is compatible with the integrated Dell Remote Access Controller (iDRAC) baseboard management controller (BMC). It is named 'idrac-redfish-virtual-media'. The iDRAC Redfish Service almost entirely interoperates with the virtual media boot workflow suggested by the Redfish standard. The only difference is configuring the system to boot from the inserted virtual media. The standard workflow expects it to be referred to as a CD-ROM or floppy disk drive boot source, no different from their physical counterparts. However, the iDRAC refers to them as virtual boot sources, distinct from their physical counterparts. Presently, the standard does not define virtual CD-ROM nor virtual floppy disk drive boot sources. However, the iDRAC provides a Redfish OEM extension for setting the system to boot from one of those virtual boot sources. To circumvent the above issue, the Python class which implements 'idrac-redfish-virtual-media' is derived from the class which implements the generic, vendor-independent 'redfish-virtual-media' interface. It overrides the method which sets the boot device to facilitate use of the aforementioned iDRAC Redfish Service OEM extension. The idrac hardware type declares support for that new interface implementation, in addition to all boot interface implementations it has been supporting. The priority order is retained by assigning the new 'idrac-redfish-virtual-media' the lowest priority. A new idrac hardware type Python package dependency is introduced. It is on 'sushy-oem-idrac'. [1] https://pypi.org/project/sushy-oem-idrac/ Co-Authored-By: Richard G. Pioso <richard.pioso@dell.com> Story: 2006570 Task: 36675 Change-Id: I416019fc1ed3ab2a3a3dbc4443571123ef90e327 |
||
|---|---|---|
| api-ref | ||
| devstack | ||
| doc | ||
| etc | ||
| ironic | ||
| playbooks | ||
| releasenotes | ||
| tools | ||
| zuul.d | ||
| .gitignore | ||
| .gitreview | ||
| .mailmap | ||
| .stestr.conf | ||
| babel.cfg | ||
| bindep.txt | ||
| CONTRIBUTING.rst | ||
| driver-requirements.txt | ||
| LICENSE | ||
| lower-constraints.txt | ||
| README.rst | ||
| requirements.txt | ||
| setup.cfg | ||
| setup.py | ||
| test-requirements.txt | ||
| tox.ini | ||
Ironic
Team and repository tags
Overview
Ironic consists of an API and plug-ins for managing and provisioning physical machines in a security-aware and fault-tolerant manner. It can be used with nova as a hypervisor driver, or standalone service using bifrost. By default, it will use PXE and IPMI to interact with bare metal machines. Ironic also supports vendor-specific plug-ins which may implement additional functionality.
Ironic is distributed under the terms of the Apache License, Version 2.0. The full terms and conditions of this license are detailed in the LICENSE file.
Project resources
- Documentation: https://docs.openstack.org/ironic/latest
- Source: https://opendev.org/openstack/ironic
- Bugs: https://storyboard.openstack.org/#!/project/943
- Wiki: https://wiki.openstack.org/wiki/Ironic
- APIs: https://docs.openstack.org/api-ref/baremetal/index.html
- Release Notes: https://docs.openstack.org/releasenotes/ironic/
- Design Specifications: https://specs.openstack.org/openstack/ironic-specs/
Project status, bugs, and requests for feature enhancements (RFEs) are tracked in StoryBoard: https://storyboard.openstack.org/#!/project/943
For information on how to contribute to ironic, see https://docs.openstack.org/ironic/latest/contributor