876a9d4027
When using drivers like `networking-generic-switch`, there can be issues with changing the VLAN the server is attached to. Currently, the instance will still continue to attempt to boot, in some cases the instance can go into ACTIVE (if the server happens to be on the provisioning network already), but the server is not attached to the correct VLAN, generally causing the network to fail to come up. If we look at the ports, they are marked as binding failed. This is something that Nova checks for after doing the port update to attach the binding information. Lets add that check into Ironic, such that the above build will fail with a good hint at where to look for problems (namely Neutron). Change-Id: I3811941a3dff0a9f968258d05cc020e1f52e3e40
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