feb3205943
If an Ironic Node is connected to multiple physnets, and wants to connect to a Neutron VIF whose network has segments in multiple physnets it may be unclear which one to connect to. If the VIF is already allocated to a subnet with a segment mapping, this can be used to resolve the process to a physnet. When a network uses Neutron routed segments, this patch first checks the port's fixed_ips to see if a segment/physnet can be determined from the subnet it is attached to. If this cannot be identified (or fixed_ips is unset), the behaviour falls back to returning all physnets available in the segmented network. A similar change in Neutron was made in I56b22820d29b2d57faf28a2f9b685ab0b2c924b4 Change-Id: Ie693257cdb8c44eeaf49cec9678de047f35d5221
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