
Multi-node grenade jobs will fail if we upgrade nova as the minimum required API for nova to communicate with ironic was upgraded. Our goal for multi-node grenade is to test rolling upgrades. The scenario we envision for rolling upgrades to be done is: 1) Upgrade ironic-conductor services one by one. This means old ironic-api services communicating with new and old ironic-conductor services. This is what the multi-node grenade job tests. 2) Upgrade ironic-api services. 3) Upgrade nova In this upgrade procedure we should not be running updated nova with old ironic-api services. This patch fixes that. Closes-Bug: #1706418 Change-Id: I85c607ae7d031e4cabcb505915aca7e88df166aa
Team and repository tags
Ironic
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://git.openstack.org/cgit/openstack/ironic
- Bugs: https://bugs.launchpad.net/ironic
- Wiki: https://wiki.openstack.org/wiki/Ironic
- APIs: https://developer.openstack.org/api-ref/baremetal/index.html
Project status, bugs, and requests for feature enhancements (RFEs) are tracked on Launchpad: https://launchpad.net/ironic
For information on how to contribute to ironic, see https://docs.openstack.org/ironic/latest/contributor