* In tear_down_agent: lock down the agent and keep the node powered on. * In boot_instance: reboot the node instead of powering it on. * In tear_down_inband_cleaning/service: avoid powering off the node. * In tear_down_service: lock down the agent before tearing down. * In tear_down and clean_up: do not power off, reboot after clean-up. * In rescue/unrescue: use one reboot instead of power off/on. Not locking down in tear_down_inband_cleaning because the node will not end up on a tenant network (and lockdown may disrupt fast-track). Depends-On: https://review.opendev.org/c/openstack/ironic-python-agent/+/934234 Partial-Bug: #2077432 Change-Id: Ib2297ec5b69df6b2ecd11942fb8fdc9d640de6bc
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://bugs.launchpad.net/ironic/+bugs
- 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 Launchpad: https://launchpad.net/ironic
For information on how to contribute to ironic, see https://docs.openstack.org/ironic/latest/contributor