
This change moves multinode jobs to be leveraged across multiple "compute" nodes with an increased amount of memory, which increases the overall test resources available and limits controller node hot spotting for deployment operations. This effectively chagnes multinode jobs from being a single compute node with a single controller node, to two compute nodes and a single controller node. The controller node's hosted virtual machines is also dialed back. This was done to eliminate usage of tinyipa in favor of a more realistic Centos based IPA ramdisk, and also removes fallback logic to use tinyipa on more limited resource nodes. Change-Id: Ib52f7039072901ce72ac96e660d35a10cca59737 Signed-off-by: Julia Kreger <juliaashleykreger@gmail.com>
Ironic
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